Merged
Conversation
jasonmalinowski
approved these changes
Dec 4, 2025
dibarbet
reviewed
Dec 4, 2025
| <PropertyGroup> | ||
| <NetRoslyn>net9.0</NetRoslyn> | ||
| <NetRoslynAll>net8.0;net9.0</NetRoslynAll> | ||
| <NetRoslynAll>net8.0;net9.0;net10.0</NetRoslynAll> |
Member
There was a problem hiding this comment.
Can we get rid of net9 now, and switch NetRoslyn to net10? Seems like its mostly for test utilities and things?
Member
Author
There was a problem hiding this comment.
I can attempt that as a follow up.
dibarbet
approved these changes
Dec 4, 2025
This was referenced Dec 9, 2025
Merged
jjonescz
added a commit
that referenced
this pull request
Jan 14, 2026
Follow up on #81545 (comment).
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Missed as part of building the Roslyn LSP against net10.0 was also building our libraries against net10.0.