Target .NET 10 / net10.0 #105343
Description
This issue tracks the infrastructure work that is required to target net10.0 for producing .NET 10 builds. The work tracked here usually starts happening when we branch-off main for .NET 9 RC2 in mid August.
Phase 1 - Branding
The branding work needs to happen in a separate PR from the re-targeting work and must not update the assembly version. This means that the AssemblyVersion property needs to be hardcoded to 9.0.0.0 here:
Line 22 in d8a642f
- Status box. Tick to mark phase 1 as completed.
Phase 2 - Re-targeting
After the branding work is done, the TFM re-targeting work can happen. There's a long list of things to do. For reference, here's the PR from last year for net9.0.
- Add dotnet10 & dotnet10-transport NuGet feeds.
- Update TFM properties so that
NetCoreAppCurrent=net10.0,NetCoreAppPrevious=net9.0andNetCoreAppMinimum=net8.0. - Update the globally set AssemblyVersion back to
$(MajorVersion).$(MinorVersion).0.0. - Update the ApiCompat baseline versions to the latest officially released package version (should be P7 if this is worked on in August). Add a TODO marker and file an issue to track updating this version to 9.0.0 GA in November.
- Update hardcoded 9.0.0.0 assembly versions in CompatibilitySuppressions.xml files (APICompat config).
- Remove the
DisablePackageBaselineValidationproperty and its comment so that we have APICompat validation for new packages during re-targeting.
WIP - Add more to this list
Phase 3 - Clean-up
- Eventually remove net9.0 NuGet feeds when all moving dependencies are on the dotnet10 feeds: Remove dotnet9 feeds from NuGet.config when dependencies publish into dotnet10 feeds #106593
- Change
set(PRERELEASE 1)to 0 in eng/native/configureplatform.cmake in therelease/9.0branch so new compiler warnings don't fail the servicing build.