Add .NET 10 build targets #454
Merged
Conversation
This file contains hidden or 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
vmoroz
approved these changes
Aug 3, 2025
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.
This change adds
net10.0build targets for all the projects. The build targets are conditional on use of the .NET 10 SDK inglobal.json, which is not yet updated. So while official builds will not include .NET 10 yet, it is easy to manually updateglobal.jsonfor testing.Tests found one major compatibility issue with .NET 10, which is that the runtime type builder is more strict about type attributes and interface method implementations than it was previously. So there are lots of code updates in
SymbolExtensions.csto comply with the new validations when converting from compiler symbols to runtime types. After that fix, all unit tests are passing on .NET 10.