Add net10.0 to SupportedNetFrameworks, drop net9.0 (EOL May 12 2026)#7976
Add net10.0 to SupportedNetFrameworks, drop net9.0 (EOL May 12 2026)#7976Rolling2405 wants to merge 1 commit intomicrosoft:mainfrom
Conversation
net9.0 STS reaches end-of-life on May 12, 2026. The repository has already moved in this direction: TargetFrameworks.cs in the test infrastructure lists net10.0 as primary with net8.0 as secondary, and the test utilities no longer reference net9.0. Update SupportedNetFrameworks from 'net8.0;net9.0' to 'net8.0;net10.0' to align the shipped package TFMs with this trajectory. All source and test projects using the \ property will automatically pick up the net10.0 TFM. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Pull request overview
Updates the repository’s shared target framework configuration to prefer .NET 10 over .NET 9, with accompanying Arcade/toolset dependency bumps.
Changes:
- Update
SupportedNetFrameworksfromnet8.0;net9.0tonet8.0;net10.0. - Bump Arcade SDK / toolset dependency versions (global.json + eng version files).
- Add an
eng/commonnote indicating the folder is Arcade-sourced.
Reviewed changes
Copilot reviewed 5 out of 5 changed files in this pull request and generated 2 comments.
Show a summary per file
| File | Description |
|---|---|
| global.json | Updates the pinned Arcade MSBuild SDK version. |
| eng/common/AGENTS.md | Documents that eng/common is Arcade-owned and overwritten by automation. |
| eng/Versions.props | Updates templating + MSTest/MTP version properties. |
| eng/Version.Details.xml | Updates Arcade + MSTest/MTP dependency versions and SHAs. |
| Directory.Build.props | Switches SupportedNetFrameworks to include net10.0 instead of net9.0. |
| <ModernUwpMinimum>net9.0-windows10.0.17763.0</ModernUwpMinimum> | ||
| <WinUiMinimum>net8.0-windows10.0.18362.0</WinUiMinimum> | ||
|
|
||
| <SupportedNetFrameworks>net8.0;net9.0</SupportedNetFrameworks> | ||
| <SupportedNetFrameworks>net8.0;net10.0</SupportedNetFrameworks> |
There was a problem hiding this comment.
ModernUwpMinimum is still set to a net9.0-* TFM. Because several projects include $(ModernUwpMinimum) in their TargetFrameworks, this change will still build/pack a net9.0 target even though SupportedNetFrameworks dropped net9.0. If the intent is to fully drop net9.0, update ModernUwpMinimum accordingly (or adjust the PR title/description to clarify that net9.0 is still required for Modern UWP).
| "msbuild-sdks": { | ||
| "Microsoft.DotNet.Arcade.Sdk": "11.0.0-beta.26229.1", | ||
| "Microsoft.DotNet.Arcade.Sdk": "11.0.0-beta.26230.2", | ||
| "MSBuild.Sdk.Extras": "3.0.44" |
There was a problem hiding this comment.
PR description states this is a single-property change in Directory.Build.props, but this PR also updates Arcade SDK + toolset dependency versions (and adds eng/common/AGENTS.md). Please update the PR description (or split into separate PRs) so reviewers/CI owners can clearly see why the dependency bumps are included.
| <WinUiMinimum>net8.0-windows10.0.18362.0</WinUiMinimum> | ||
|
|
||
| <SupportedNetFrameworks>net8.0;net9.0</SupportedNetFrameworks> | ||
| <SupportedNetFrameworks>net8.0;net10.0</SupportedNetFrameworks> |
There was a problem hiding this comment.
I don't think we should do that. It's completely fine to still keep net9.0, and there is no obvious need to add net10.0.
Users today can already target net10.0 and will be consuming our net9.0 artifacts without any problem.
Summary
Updates SupportedNetFrameworks in Directory.Build.props from
et8.0;net9.0 to
et8.0;net10.0.
.NET 9.0 STS reaches end-of-life on May 12, 2026. The repository has already been moving in this direction:
et10.0 as primary with
et8.0 as secondary (no net9.0)
This single-property change propagates
et10.0 automatically to all ~30 source and test projects that reference .
Changes
et8.0;net9.0 →
et8.0;net10.0
Note on closed PR #6762
That PR was opened in October 2025 when net10.0 was still pre-release. Now that net10.0 is GA and net9.0 is at EOL, the timing is right.