Skip to content

Conversation

@ViktorHofer
Copy link
Member

@ViktorHofer ViktorHofer commented Nov 20, 2025

Contributes to #118583

For reference, this was last year's PR for net10.0. #106599

@github-actions github-actions bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 20, 2025
@dotnet-policy-service dotnet-policy-service bot added the linkable-framework Issues associated with delivering a linker friendly framework label Nov 20, 2025
@am11 am11 added area-Infrastructure and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Nov 26, 2025
@dotnet-policy-service
Copy link
Contributor

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

@am11
Copy link
Member

am11 commented Nov 28, 2025

@ViktorHofer, does it depend on dotnet/dotnet#2271?

@ViktorHofer
Copy link
Member Author

Not necessarily but it would be better to get that in first. I included the branding update in this PR (see eng/Versions.props changes).

@ViktorHofer
Copy link
Member Author

ViktorHofer commented Dec 3, 2025

D:\a_work\1\s.dotnet\sdk\10.0.100-rc.2.25502.107\Sdks\Microsoft.NET.Sdk\targets\Microsoft.NET.TargetFrameworkInference.targets(188,5): error NETSDK1045: The current .NET SDK does not support targeting .NET 11.0. Either target .NET 10.0 or lower, or use a version of the .NET SDK that supports .NET 11.0. Download the .NET SDK from https://aka.ms/dotnet/download [D:\a_work\1\s\src\installer\tests\Assets\Projects\HostApiInvokerApp\HostApiInvokerApp.csproj]

Need this property: https://github.com/dotnet/runtime/blob/69310d88a431951addcc65ad093ea59528f80c48/Directory.Build.targets#L56C6-L56C30

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the .NET runtime repository to target .NET 11.0, migrating from .NET 10.0. This is a major version bump that touches numerous configuration files, test infrastructure, documentation, build scripts, and package manifests across the repository.

Key changes:

  • Updated version numbers from 10.0 to 11.0 and net10.0 to net11.0 throughout the codebase
  • Updated compatibility suppressions and baselines to reference net11.0
  • Modified workload manifests to add net10.0 as a previous version while making net11.0 current
  • Updated test infrastructure and configuration files
  • Modified documentation to reflect the new version

Reviewed changes

Copilot reviewed 111 out of 113 changed files in this pull request and generated no comments.

Show a summary per file
File Description
Directory.Build.props Updated NetCoreAppCurrentVersion from 10.0 to 11.0, adjusted minimum and previous versions
eng/Versions.props Updated major version to 11, revised package versioning scheme, added net10 package version references
eng/build.sh, eng/build.ps1 Updated framework examples from net10.0 to net11.0
eng/packaging.targets Added package validation baseline framework exclusions for net8.0 and net9.0
eng/pruning.targets New file to use .NET 10 pruning data temporarily for .NET 11
eng/intellisense.targets Hardcoded to use net-10.0 intellisense package temporarily
eng/testing workload targets Added net10 workload testing support, commented out net7 combinations
src/mono/nuget files Added Microsoft.NET.Workload.Mono.Toolchain.net10.Manifest package and related localization
src/libraries compatibility files Updated suppressions from net10.0 to net11.0 references
src/mono/wasm test projects Updated target frameworks from net10.0 to net11.0
src/mono/wasm templates Updated template identities and framework choices from net10.0 to net11.0
docs Updated documentation examples and paths from net10.0 to net11.0
Various test and build configs Updated framework and version references throughout

@lewing
Copy link
Member

lewing commented Dec 9, 2025

SDK/Blazor Templates tracking issue is dotnet/sdk#50295
Aspnetcore pr is dotnet/aspnetcore#64627

@kotlarmilos
Copy link
Member

I updated the Apple mobile jobs to run on the scouting queues to get a clean run. The default queues are not functional at the moment. They will be fixed in a separate PR.

@kotlarmilos
Copy link
Member

iOS mobile smoke tests passed.

Screenshot 2025-12-09 at 15 31 53

tvOS is currently blocked by infrastructure issues that the engineering team is mitigating. I am reverting queue changes for now as they are in #122341.

For escaping build analysis please use dotnet/dnceng#6440

@steveisok
Copy link
Member

Let's try to push this through today if the failures are reasonable and can be worked in a follow up.

@ericstj
Copy link
Member

ericstj commented Dec 9, 2025

/ba-g only test failure is timeout

['System.Threading.Tests' END OF WORK ITEM LOG: Command timed out, and was killed]

https://helixr1107v0xdeko0k025g8.blob.core.windows.net/dotnet-runtime-refs-pull-121853-merge-fca074267dbe4ce4b8/System.Threading.Tests/1/console.7c75b9d4.log?helixlogtype=result

Same test is passing on MacOS in other configurations. Merging.

@steveisok steveisok merged commit 6936d80 into main Dec 9, 2025
172 of 179 checks passed
@steveisok steveisok deleted the net11 branch December 9, 2025 18:56
@marcpopMSFT
Copy link
Member

@DonnaChen888 once this flows to the dotnet/dotnet repo and we get a build, we should be able to update the global.json in dotnet/sdk and do the next two steps (update the templates to target 11 and update the SDK to target 11).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area-Infrastructure linkable-framework Issues associated with delivering a linker friendly framework

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.