Document .NET 10 SDK version requirements breaking change#48923
Merged
Document .NET 10 SDK version requirements breaking change#48923
Conversation
Co-authored-by: gewarren <24882762+gewarren@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] [Breaking change]: Version requirements for the .NET 10 SDK
Document .NET 10 SDK version requirements breaking change
Oct 6, 2025
gewarren
approved these changes
Oct 8, 2025
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR documents the breaking change for .NET 10 SDK version requirements, specifically addressing the updated Visual Studio version requirements for RC 2 and GA releases. The breaking change establishes that Visual Studio 17.14 is now required to load the .NET 10.0.100 SDK, while targeting net10.0 requires Visual Studio 18.0 (Visual Studio 2026) or later.
- Created comprehensive breaking change documentation explaining Visual Studio version requirements for .NET 10 SDK
- Updated versioning tables and support documentation to reflect the new requirements
- Added navigation entries to make the breaking change easily discoverable
Reviewed Changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
docs/core/compatibility/sdk/10.0/version-requirements.md |
New breaking change documentation detailing Visual Studio version requirements for .NET 10 SDK |
docs/core/compatibility/10.0.md |
Added entry for the version requirements breaking change to the main compatibility index |
docs/core/compatibility/toc.yml |
Added navigation entry for the new breaking change documentation |
docs/core/porting/versioning-sdk-msbuild-vs.md |
Updated versioning tables with .NET 10.0.100 requirements and added RC 2 preview entry |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
meaghanlewis
approved these changes
Oct 14, 2025
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
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.mdthat explains:net10.0Updated Index and Navigation
docs/core/compatibility/10.0.mddocs/core/compatibility/toc.ymlfor easy discoveryUpdated Versioning Tables
Updated
docs/core/porting/versioning-sdk-msbuild-vs.mdwith:net9.0in the minimum versionnet10.0is officially supported in Visual Studio 18.0+ onlyImpact
Developers using .NET 10 SDK will need to:
net10.0in 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.
Internal previews