Microsoft Ships .NET 11 Release Candidate 1 with Go-Live License

AIDeveloper44 Team

Overview of the .NET 11 RC1 Milestone

Microsoft has announced the release of .NET 11 Release Candidate 1, marking a critical step toward the framework's next major version. Unlike standard preview milestones, Release Candidate builds arrive with an official "go-live" support license. This policy guarantees production-level support from Microsoft, enabling engineering organizations to deploy RC1 builds directly into production environments prior to general availability.

Alongside the runtime and framework packages, the release is supported across core development environments. Microsoft has aligned .NET 11 RC1 with the Visual Studio 2026 Insiders release on Windows, as well as Visual Studio Code workflows through the updated C# Dev Kit extension.

Runtime and Base Class Library Additions

The base class libraries and runtime internals received multiple low-level improvements aimed at cross-platform consistency, cryptographic throughput, and system-level diagnostics. In the runtime layer, .NET 11 RC1 adds in-process crash reporting mechanisms on Unix platforms, allowing applications to retain debugging details during fatal failures without external daemon intervention. Furthermore, mathematical operations involving 16-bit floating-point types (`Half`) now leverage dedicated FP16 hardware instructions on compatible architectures.

Core libraries have expanded Unix platform parity and security capabilities. Notable updates include:

• Network and Process APIs: Linux developers gain dedicated DNS record resolution APIs, while Unix environments receive support for TLS channel binding. The framework also adds routines to inspect process termination status and send process signals directly.
• Cryptography: The cryptographic stack incorporates AES Key Wrap functionality alongside hardware-accelerated authenticated encryption routines specifically optimized for Apple platforms.
• Data Serialization: `System.Text.Json` adds closed-type polymorphism, union support, validation for asynchronous options, and expanded parsing for specialized numeric types and binary schemas.
• Memory and Compression: Span-based constructors are now supported for `BitArray`, and developers can reuse compression encoder and decoder instances to minimize heap allocations.

SDK, MSBuild, and NuGet Enhancements

Developer tooling has also been adjusted in SDK version 11.0.100-rc.1. Command-line test runs via `dotnet test` now offer refined run-level controls, customizable result layouts, and specific enhancements aimed at mobile application test automation. For containerized deployments, built-in container publishing now enforces reproducible images and automatically avoids redundant layer uploads.

In the build system, MSBuild introduces native functionality to construct and unpack `.tar` archives, reducing reliance on third-party utilities. Globs defined across project files are also exposed directly to external build tooling for more reliable evaluation. Concurrently, NuGet improves project evaluation caching during `dotnet pack` routines and handles package vulnerability warnings cleanly in environments where warnings are treated as build errors.

Languages: C# and F# Updates

Language toolchains have advanced alongside the runtime updates. In C#, the compiler stabilizes support for unions and closed class hierarchies, easing domain modeling and functional pattern matching across core libraries and application layers. Refinements have also been added to the "Unsafe Evolution" language proposal to maintain type safety when dealing with pointer manipulations and direct memory blocks.

F# receives modern syntax enhancements, such as record spreads, formal record constructors, direct delegate construction, and more memory-efficient interpolated strings. Additionally, reflection-free formatting routines have been introduced for records and discriminated unions, boosting logging and printing performance in Native AOT and constrained runtimes.

ASP.NET Core and Web Infrastructure

Web development workloads receive functional updates across server-side and client-side stacks. In ASP.NET Core, authentication APIs within SignalR have been finalized to manage token refresh cycles cleanly. This is accompanied by official refresh support in the TypeScript SignalR client, ensuring long-running connections maintain valid credentials without manual teardowns. Blazor Server circuits also adapt automatically following authentication refresh events.

For API contract management, OpenAPI generation now honors obsolete attribute markers and allows developers to target distinct configuration environments during build-time OpenAPI document emission. ASP.NET Core Negotiate authentication has been wired to support TLS channel binding. Microsoft has also included experimental Blazor AI components tailored for agent-driven user interfaces.

Availability and Installation

Installers and binary packages for the .NET 11 RC1 SDK and runtimes (including the base .NET Runtime, ASP.NET Core Runtime, and .NET Desktop Runtime) are distributed across Windows, macOS, and Linux platforms. The full SDK payload can be retrieved directly through Microsoft's Windows x64 installer page, container images, or via cross-platform installation scripts.

Enjoyed this?

Get more posts like this delivered to your inbox.

Subscribe