.NET 10 Release Candidate 2

[jongalloway]

.NET 10 Release Candidate 2 is now available. This is our second and final release candidate which comes with a go-live support license so you can confidently use this release for your production applications. This release of .NET 10 is supported in the new Visual Studio 2026 Insiders release alongside Visual Studio Code with the C# Dev Kit. Check out the full release notes below and get started today.

This release contains the following highlights and improvements.

🛠️ SDK

• Use .NET MSBuild Tasks with .NET Framework MSBuild
• Full Release Notes

📱 .NET MAUI

• Microphone permission
• SafeAreaEdges
• XAML Source Generation
• Android API 36.1
• Xcode 26
• Full Release Notes

🎁 Entity Framework Core

• Numerous fixes for the new EF complex JSON support
• Stop spanning all migrations with a single transaction
• Use ExecutionStrategy for query execution (for retrying)
• Analyzer warnings for string concatenation in raw SQL APIs
• Full Release Notes

📚Libraries

This release candidate is focused on quality improvements and does not contain new Libraries features.

• Full Release Notes

⏱️Runtime

This release candidate is focused on quality improvements and does not contain new Runtime features.

• Full Release Notes

C#

This release candidate is focused on quality improvements and does not contain new C# features.

F#

This release candidate is focused on quality improvements and does not contain new F# features.

Visual Basic

This release candidate is focused on quality improvements and does not contain new Visual Basic features.

🌐 ASP.NET Core & Blazor

This release candidate is focused on quality improvements and does not contain new ASP.NET Core features.

• Full Release Notes

🖥️ Windows Forms

This release candidate is focused on quality improvements and does not contain new Windows Forms features.

• Full Release Notes

🖥️ Windows Presentation Foundation (WPF)

This release candidate is focused on quality improvements and does not contain new WPF features.

• Full Release Notes

📦 Container Images

This release candidate is focused on quality improvements and does not contain new container features.

• Full Release Notes

🚀 Get started

To get started with .NET 10, install the .NET 10 SDK.

If you're on Windows, we recommend installing the latest version of Visual Studio 2026 Insiders. Read more about this new release on the Visual Studio blog and release notes.

You can also use Visual Studio Code and the C# Dev Kit extension with .NET 10.

🔔 Stay up-to-date with .NET 10

You can stay up-to-date with all the features of .NET 10 with:

• What's new in .NET 10
• What's new in C# 14
• What's new in .NET MAUI
• What's new in ASP.NET Core
• What's new in Entity Framework Core
• What's new in Windows Forms
• What's new in WPF
• Breaking Changes in .NET 10
• .NET 10 Releases

Additionally, be sure to subscribe to the GitHub Discussions RSS news feed for all release announcements.

[bairog]

What is supported way to target .NET 10 RC2 in a production code? According to .NET 10 RC2 download page and this article header targeting net10 will require VS 2026. .NET 10 RC2 has a go-live support license but VS 2026 Preview3 is not allowed for production code:

the Insiders Channel is not intended for use in production

And we still have no clear answer here - which specific scenarios are known to be broken when using .NET 10 and VS 2022? What has changed between .NET 10 Preview 7 (supports VS 2022) and RC1 (supports only VS 2026)?

This is a warning only as not every scenario is impacted so some customers may be successful using VS 2022 but we won't be testing with that configuration and we know not all scenarios will work.

Thank you.

[KalleOlaviNiemitalo]

which specific scenarios are known to be broken when using .NET 10 and VS 2022?

One was filed just now at dotnet/msbuild#12669.

[baronfel]

It's also worth noting that .NET is a separate product from Visual Studio. This year the release schedules have happened to line up such that there is no production-supported VS version that drives the SDK, but for many teams they aren't publishing from Visual Studio - they use CI workflows to build assets using the go-live supported SDK tooling and have great success doing so. Or they use editors other than VS that have different support cycles or functionality for their teams.

[Kobi-Blade]

Since both .NET and Visual Studio are Microsoft products, you'd expect their release schedules to be better aligned.

Right now, it's a bit of a mess. The .NET team says .NET 10 RC2 is production ready and recommends using it with Visual Studio 2026. But at the same time, the Visual Studio team is saying 2026 is still in preview and not meant for production use. That kind of mixed messaging makes it hard for us to adopt .NET 10 confidently in a stable environment.

It would go a long way if the product teams coordinated better, it’s not just about syncing dates, it’s about giving us a clear and consistent messaging.

[n00j]

The NETStandard pack seems missing in the linux download (https://dotnet.microsoft.com/en-us/download/dotnet/thank-you/sdk-10.0.100-rc.2-linux-x64-binaries) packs/NETStandard.Library.Ref. Was that intentional?

[yrintsoaemmanuel]

cpp

[gimlichael]

After update to RC2, libraries relying on System.Net.Http (for .NET Framework consumers) does not work anymore. Both locally and in CI/CD pipelines on GitHub. I cannot find anything that suggest this in the release notes / breaking changes, hence I write it here.

It triggers a CS0012 with The type 'MediaTypeHeaderValue' is defined in an assembly that is not referenced. You must add a reference to assembly 'System.Net.Http, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.

Libraries has multi-target TFMs .. those with netstandard2.0 is unit tested with .NET Framework 4.8 - and this is where the problem emerges.

[gimlichael]

If you are curious here is a link to my .NET 10 matured library: https://github.com/gimlichael/Cuemon/tree/v10.0.0/preview

[gimlichael]

I asked ChatGPT as I had wasted to many hours .. haha .. sharing is caring: https://chatgpt.com/share/68f35167-fe8c-8010-8caf-f648539bdad0

TL;DR - changed PackageReference to Reference - and now it works. It would just be nice with a documentation since this is only necessary with RC2 - not RC1.

Maybe its a feature of VS 2026, actually? Which is a strange beast that you tightly couple .NET with IDE (as others has also mentioned). Come to think of it - its not .. haha .. it also fails in CI/CD .. where i get this information: D:\a\Cuemon\Cuemon\test\Cuemon.Resilience.Tests\Cuemon.Resilience.Tests.csproj : warning NU1510: PackageReference System.Net.Http will not be pruned. Consider removing this package from your dependencies, as it is likely unnecessary. [TargetFramework=net9.0] D:\a\Cuemon\Cuemon\test\Cuemon.Resilience.Tests\Cuemon.Resilience.Tests.csproj : warning NU1510: PackageReference System.Net.Http will not be pruned. Consider removing this package from your dependencies, as it is likely unnecessary. [TargetFramework=net48] D:\a\Cuemon\Cuemon\test\Cuemon.Resilience.Tests\Cuemon.Resilience.Tests.csproj : warning NU1510: PackageReference System.Net.Http will not be pruned. Consider removing this package from your dependencies, as it is likely unnecessary. [TargetFramework=net10.0].

After futher insights it is for sure a bug in RC2 as outlined by @martincostello - they do not honor what is documented: https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1510

[martincostello]

It's possible you're hitting a variant of this issue: dotnet/sdk#51265

[gimlichael]

Thanks, Martin - make sense. Happy i took the chance and now got wiser.

[ToreDemant]

Is anyone else having problems with SGEN?

PackageReference and DotNetCliToolReference are updated to the latest version:

<PackageReference Include="Microsoft.XmlSerializer.Generator" Version="[10.0.0-rc.2.25502.107]" />
<DotNetCliToolReference Include="Microsoft.XmlSerializer.Generator" Version="[10.0.0-rc.2.25502.107]" />

But get the following warning:

##[warning]SGEN(0,0): Warning SGEN1: Could not load file or assembly 'System.Runtime, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL'.

The same was the case with RC1. Could it be something like the SGEN does not consider prereleases and would there be a way to change this?

[KalleOlaviNiemitalo]

dotnet/runtime#120734 was filed for this.

[ToreDemant]

Thanks @KalleOlaviNiemitalo

[matengo]

When publishing blazor web app (wasm render mode) to Azure Container App (using right click publish in VS 2026 insiders), the client I tries to fetch a hotreload file (_content/Microsoft.DotNet.HotReload.WebAssembly.Browser/Microsoft.DotNet.HotReload.WebAssembly.Browser…) and get 404 for that one, and error in the webbrowser console and after that the app is in error state (not working)... Any ideas?

[Kobi-Blade]

Is the typical disconnect between the Visual Studio Team and .NET Team, have you tried dotnet publish?

[matengo]

It needs to be packed in a container and shipped to ACR/ACA using Net SDK (without dockerfile).. Not sure if you can do that using dotnet publish?