Microsoft releases .NET 11 with Standard Term Support
Microsoft has launched .NET 11 as a two-year Standard Term Support release, forcing organizations off unsupported .NET 8 and .NET 9 versions.

Microsoft has released .NET 11 as a Standard Term Support version with two years of support, distinct from the three-year Long Term Support cycle of .NET 10. The company announced the release at the .NET Conf 2026 virtual conference, advising organizations to move to .NET 11 or .NET 10 as .NET 8 and .NET 9 reached end of support on November 10, 2026. This year's release makes building modern applications faster and more productive, according to the .NET team, who state it includes hundreds of runtime optimizations, more responsive SDK tooling, and less overhead in everyday commands. Teams running release candidates of .NET 11 are told to move to the final build.
Support lifecycle
Enterprises must plan migration strategies as .NET 8 and .NET 9 reach end of support, with Microsoft advising movement to .NET 11 or .NET 10. .NET 10 remains the supported Long Term Support option for those seeking a three-year support window. The shift to the new Standard Term Support model for .NET 11 provides a predictable, two-year maintenance window for organizations to align with their upgrade cycles.
Security and reliability
New defensive features including SignalR authentication refresh, ZIP CRC32 validation, and package publication age controls defend against emerging threats. SignalR connections can now refresh authentication without reconnecting, improving security for persistent connections. In System.IO.Compression, reading ZIP entries now includes CRC32 validation to ensure data integrity. A new NuGet source configuration setting for minimum package publication age works as a 'cooldown' period to defend against malicious or compromised package releases. Container publishing now produces reproducible image digests through SOURCE_DATE_EPOCH, enhancing supply chain security. Zstandard compression is newly supported.
Csharp innovations
C# 15 introduces union types and closed class marking, giving developers stronger compile-time guarantees about type safety and inheritance. Union types allow a value to be one of a fixed set of existing types. Marking a class closed restricts direct derivation to its assembly, enabling exhaustiveness checking over that known set of descendants. Collection expressions can pass constructor or factory arguments through a leading with(...) element. Extension indexers let developers add indexing syntax to a receiver. Asynchronous validation lets validators await database lookups or remote calls without blocking threads.
Blazor and AI
Blazor Interactive Server gains identity management and circuit pausing, while new AI components enter prerelease as experimental features for agentic capabilities. Blazor Interactive Server components receive updated identity and can react when claims change. These apps can pause inactive circuits after a set delay to free server memory, though this feature requires an additional package and explicit configuration. New Blazor AI components support streaming chat, tool rendering, and approval flows for agent actions. These Blazor AI components are experimental and will stay prerelease throughout .NET 11, and organizations should treat these AI features as non-production features.
Additional updates include an expanded Process API giving developers control over handles a child process inherits, as well as providing suspended process starts and process signaling. In-process crash report logging, which previously worked on mobile platforms, now also works on Linux and macOS, capturing a managed stack trace, module information, and runtime state. The SDK now includes an MCP server template built on the official MCP C# SDK, and the AG-UI hosting integration is also prerelease. Microsoft's separate C# memory safety work is still in preview. The .NET team said: "The libraries also expand numeric types, DNS resolution, cryptography, and tracing configuration." Enterprises evaluating .NET 11 for upgrade planning should assess their current .NET 8 and .NET 9 deployment timelines against the two-year Standard Term Support window.





