What the RC2 announcement actually says
Paul Thurrott's coverage frames RC2 as the "final round of testing". He writes that he assumes it will be the final pre-release build. That is his inference. The .NET team's announcement calls this the second release candidate and does not say another one won't follow.
The launch timing does have a firm anchor elsewhere. Visual Studio Magazine reported that Microsoft has said .NET 11 will launch during .NET Conf 2026, which begins Nov. 10. Microsoft Learn's overview page also says general availability is expected in November 2026. Thurrott's "one month" is therefore roughly right, but it is not a date from the RC2 post.
The go-live license
RC1 was the first build with this go-live license. Visual Studio Magazine described it as the point in the development cycle when the platform first carries a go-live support license for production applications. RC2 keeps that status.
A go-live license is not the same as general availability. It means Microsoft supports production use of the build. It does not mean behavior is frozen, and the team should still run its own regression tests. This is general release-engineering practice, not something the announcement spells out.
Tooling: what works with RC2
The announcement pairs RC2 with two tool sets:
- Visual Studio 2026 Insiders. .NET 11 is supported in the new Visual Studio 2026 Insiders release alongside Visual Studio Code with the C# Dev Kit. Windows developers are told to install the latest Insiders build.
- Visual Studio Code with C# Dev Kit. Thurrott notes the kit is newly aligned to the latest .NET release.
The announcement names only these two tool sets. Don't assume a stable Visual Studio channel supports RC2 until Microsoft says so.
What's in the release
The announcement is a highlights list, not a full changelog. Each component links to its own release notes. The items below are the ones it names.
Libraries
- Incremental CBOR reading, experimental composite ML-KEM and HPKE APIs, DataAnnotations messages formatted with attribute-specific arguments, and configurable initial HTTP/2 concurrency.
- The cryptography APIs are labeled experimental. Treat them as subject to change.
Runtime
- File locking on iOS and tvOS is disabled by default. If you ship apps for those platforms and rely on file locks, check the runtime release notes.
SDK, MSBuild and NuGet
- The SDK adds quoted file-level directive values and MSBuild properties in launch-profile arguments.
- MSBuild gets faster wildcard matching during project evaluation. No benchmark is given.
- NuGet can now set a minimum package publication age from the CLI. The announcement gives no syntax or defaults. This is the kind of setting supply-chain-minded teams will want to read up on. That is my reading of the feature, not Microsoft's stated rationale.
F#
- Runtime async support, reraise in computation expressions, required named arguments for selected APIs, lower allocations in FSharp.Core collections, compiler memory usage improvements, bounded concurrent asynchronous work, and trimming and Native AOT improvements.
- "Require named arguments for selected APIs" could affect existing code, so check it against your F# projects.
ASP.NET Core
- QuickGrid virtualization APIs are no longer experimental. That is a status change for those APIs specifically, not for all of QuickGrid.
.NET MAUI
- Headings cover C# UI apps, Apple Icon Composer assets, evaluating the Apple Shell handler, XAML authoring and Hot Reload, .NET for Android, and Apple platforms (iOS, Mac Catalyst, macOS, tvOS). The post gives no detail beyond those headings.
Windows Forms
- This is the section most relevant to Windows desktop developers. The listed items are visual styles and appearance, reacting to Windows visual and accessibility settings, deferred form reveal, the Visual Basic Application Framework, suspending painting and layout during bulk updates, a new KioskModeManager component, and new designer-guiding analyzers.
- The announcement gives no API signatures, supported Windows versions or configuration steps. Read the Windows Forms release notes before planning around any of these.
Is .NET 11 "minor"?
Thurrott calls .NET 11 a minor release with many small functional and quality of life improvements. Microsoft's RC2 post makes no such characterization and quantifies no aggregate performance gain. The changes above are mostly incremental, so the description is plausible. Whether it feels minor depends on your stack. A kiosk app maker or a NuGet-policy owner may see it differently from someone on a plain ASP.NET Core service.
Release cadence
The .NET Blog's featured archive shows the path to this point. Preview 2 shipped March 10, and a Preview 7 post followed on August 11. RC1 came on September 8, then RC2 on October 13. The archive confirms the sequence but not a guaranteed GA date.
The download page also lags a little. It tells visitors that