Document .NET 10 SDK version requirements breaking change #48923
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.
Summary
This PR documents the breaking change for .NET 10 SDK version requirements, addressing issue #494516.
Changes
New Breaking Change Documentation
Created comprehensive documentation at
docs/core/compatibility/sdk/10.0/version-requirements.md
that explains:net10.0
Updated Index and Navigation
docs/core/compatibility/10.0.md
docs/core/compatibility/toc.yml
for easy discoveryUpdated Versioning Tables
Updated
docs/core/porting/versioning-sdk-msbuild-vs.md
with:net9.0
in the minimum versionnet10.0
is officially supported in Visual Studio 18.0+ onlyImpact
Developers using .NET 10 SDK will need to:
net10.0
in their projectsThis follows the established pattern from previous .NET releases where new SDKs require updated Visual Studio versions to support new framework targets.
Fixes #494516
Original prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.