Support C# 10 and C# 11 codebases #179
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
December 17, 2022 16:43
…es written in C# 10 and C# 11. In particular this adds support for file-scoped namespaces, which the parser was seeing as an error. .NET Core 2 and 3 are out of support, so remove the AspNetSimple.NetCore2 sample app, and update the other sample apps to .NET 7. Also update other NuGet package dependencies.
added 2 commits
December 17, 2022 16:58
Remove old sample app.
|
Gentle nudge @artiomchi @kevinkuszyk |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update to the latest Roslyn SDK to support running R4MVC over codebases written in C# 10 and C# 11.
In particular this adds support for file-scoped namespaces, which the parser was seeing as an error.
.NET Core 2 and 3 are out of support, so remove the AspNetSimple.NetCore2 sample app, and update the other sample apps to .NET 7.
Also update other NuGet package dependencies.
Resolves issue #177