.NET 11 Ships With Two Years of Support, and .NET 10 Stays Available as LTS

Microsoft released .NET 11 on November 10, 2026. It is a Standard Term Support (STS) release, which means it receives two years of support under the .NET support policy. The .NET Blog post also confirms that .NET 10 remains a supported Long Term Support (LTS) option.

The post says STS and LTS releases follow the same quality and servicing policies. They differ only in how long support lasts. For teams choosing between them, the decision comes down to upgrade cadence and how long a given runtime must stay in production, not to differences in patch rigor.

On the language and runtime side, C# 15 is the default language version for projects targeting .NET 11. .NET MAUI, the framework for mobile and desktop apps, adopts CoreCLR as its default runtime in .NET 11. That brings client app packaging closer to the runtime used by server workloads. The libraries also add built-in Zstandard compression, a widely used compression algorithm, so developers no longer need a separate package to use it.

ASP.NET Core, the web framework, adds asynchronous validation and support for OpenAPI 3.2. OpenAPI is the standard format for describing web APIs. Both changes touch the request pipeline and the API contract tooling that many teams use to generate clients and documentation, so they are likely to be among the first items reviewed during migration.

The announcement also points to faster developer tools and new capabilities for web, mobile, desktop, and AI applications.

Several related items appeared in October and early November. On October 19, the .NET Blog published guidance on preparing .NET MAUI apps for Xcode 27, covering scene lifecycle changes. Out-of-band security updates in October addressed a Brotli decoder vulnerability and a tarball ownership vulnerability. On October 27 and 29, Microsoft described Blazor collaborations with Infragistics and Syncfusion, covering free, open-source components and developer tooling. The Infragistics work also includes new .NET 11 analyzers. On November 3, the blog described delivering agent skills in NuGet packages so that models can receive up-to-date library documentation. On November 5, Microsoft published a post on modernizing .NET apps for Windows Arm64 with the GitHub Copilot upgrade agent. The same day, it opened the 2026 .NET Developer Survey, which takes about 15 minutes and will guide future .NET investments. A November servicing updates recap for .NET and .NET Framework has also been published.

The release is being promoted through .NET Conf 2026, running November 10 to 13. Product team sessions take place on November 10 and 11, followed by two days of community sessions.

In my view, the most practical question for enterprise platform teams is how the STS window fits their upgrade calendar. A two-year horizon suits organizations that already upgrade annually. Teams that move more slowly will keep weighing .NET 10 as their LTS baseline. Because both tracks share servicing policy, that choice carries no quality penalty on either side.

The broader context here is the steady consolidation of the .NET runtime across client and server. CoreCLR as the MAUI default, the Zstandard addition, and the agent-oriented tooling all point toward a platform where one runtime, one language version, and one toolset cover more of the application surface. For developers, the practical gain is fewer runtime-specific seams to maintain. That gain will become easier to assess once the .NET 11 previews and conference sessions yield concrete migration guidance.