Fix the VS warning to state 18.0 is required for net10.0 targeting #50737
+1
−1
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
This was referenced Sep 10, 2025
akoeplinger
approved these changes
Sep 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
There's a customer warning message when a customer tries to target a newer runtime than is supported in the SDK they are using and they are building in VS. The scenario for this is using VS 2022 17.14 to target net10 and having a 9.0 SDK.
The message was hardcoded to 17.16 back when net9 first released as we didn't know what the VS version number would be. Now that that's been announced, we should fix this.
Customer impact
VS will tell customers to use 18.0 if trying to target net10.0 within VS 17.14 or below
Regression?
No
Risk
Low