.NET 11 Is Out and .NET 8 and 9 Lost Support: Upgrade to .NET 10 or .NET 11?

.NET 11 and C# 15 have shipped, and .NET 8 and 9 are out of support. Which release should you move to, what is new, and how do you plan the upgrade?

Published 6 min read

.NET 11 shipped on November 10, 2026, and on the same day .NET 8 and .NET 9 stopped receiving fixes. If your services, APIs or desktop apps still run on either of them, every security patch Microsoft ships from now on will skip you. This article covers the decision you have to make first (.NET 10 or .NET 11), what C# 15 and the rest of .NET 11 bring, and a practical checklist for the move.

What changed on November 10

According to Microsoft's announcement, .NET 11 is a Standard Term Support (STS) release with two years of support. The same day, the final patches for the previous releases came out: 8.0.34 for .NET 8 and 9.0.23 for .NET 9. The .NET support policy now lists both as out of support.

"Out of support" does not mean your application stops working. It means no more security fixes, no more bug fixes, and growing friction with tooling, container images and libraries that move on. For anything internet-facing or handling customer data, that is a risk you have to plan around, not ignore.

.NET 10 or .NET 11?

Microsoft's guidance is simple: choose .NET 11 for the latest capabilities, or .NET 10 if its Long Term Support (LTS) lifecycle fits you better. The support table makes the choice more interesting than usual:

Release

Type

Released

End of support

.NET 11

STS

November 10, 2026

November 14, 2028

.NET 10

LTS

November 11, 2025

November 14, 2028

.NET 9

STS

November 12, 2024

November 10, 2026

.NET 8

LTS

November 14, 2023

November 10, 2026

.NET 10 and .NET 11 end support on the same day. That is how the policy works: LTS releases get three years, and STS releases get one year after the next release, which comes to two years because releases ship every twelve months. Microsoft also states that LTS and STS releases have the same quality and servicing; only the length of support differs.

So for a team leaving .NET 8 or 9 today, the support window is identical either way. The real question is about features and risk:

  • Choose .NET 11 if you want C# 15, the faster SDK and the new libraries, and your dependencies already support it.

  • Choose .NET 10 if a key dependency (a database provider, a UI library, an internal package) has not yet been validated on .NET 11, or if your organisation's rules require an LTS release.

C# 15: union types and closed hierarchies

C# 15 is the default language version for projects targeting .NET 11, and its headline feature is union types: a value that is exactly one of a declared set of types, with exhaustiveness checking in switch expressions. Microsoft's example is a product lookup that either finds a product or reports that it was not found:

public sealed record Product(int Id, string Name);
public sealed record ProductNotFound(int Id);
public union ProductLookup(Product, ProductNotFound);

string message = result switch
{
Product product => $"Found {product.Name}",
ProductNotFound missing => $"No product with ID {missing.Id}",
};

The return type now tells every caller exactly which outcomes it must handle. You no longer need object, a marker interface or an artificial base class to return "either this or that", and the compiler can check that nothing is forgotten. For backend code full of "success or a specific failure" results, this removes a whole category of runtime surprises.

C# 15 also adds closed hierarchies: a closed class limits direct derivation to its own assembly, so the compiler knows every subtype and can check patterns over them. Microsoft's rule of thumb: unions combine existing types; closed hierarchies fit models where you own the inheritance.

Smaller additions include collection expression arguments (for example, building a HashSet with a case-insensitive comparer inside [...] syntax), extension indexers, and labeled break and continue. None of these need the preview language version. The separate memory-safety work is still in preview.

Smaller changes that save time every day

Some of the most useful changes are in the tooling:

  • The SDK now uses a Native AOT CLI host by default, so commands such as help and version queries run without starting the managed CLI.

  • The MSBuild server stays warm between CLI invocations by default, which cuts repeated startup work.

  • NuGet gains a minimum package publication age setting, so teams can wait before newly published package versions become eligible. Microsoft notes it is an extra policy control, not a replacement for vulnerability checks or dependency reviews.

  • Container publishing produces reproducible image digests through SOURCE_DATE_EPOCH and skips redundant layer uploads.

  • dotnet new mcpserver creates a Model Context Protocol server project with a working sample tool, built on the official MCP C# SDK.

Libraries, ASP.NET Core and EF Core

In the base libraries:

  • built-in Zstandard compression;

  • simpler process execution: one-shot methods that run a process and capture its output and exit status;

  • four in-memory stream adapters (ReadOnlyMemoryStream, WritableMemoryStream, ReadOnlySequenceStream, StringStream) that expose existing data as a Stream without copying it first;

  • LINQ FullJoin, which keeps unmatched items from both sides. It is useful for reconciliation, such as comparing two inventories.

In ASP.NET Core, validation can now be asynchronous through new async DataAnnotations APIs, so a validator can await a database lookup instead of blocking a thread. Generated documents default to OpenAPI 3.2, and Blazor adds a CacheView component that caches the rendered output of a component subtree during static server-side rendering. .NET MAUI now uses CoreCLR as its default runtime.

EF Core 11 requires .NET 11. Its SQL Server vector search features are experimental, so treat them as something to evaluate rather than build production features on today.

An upgrade checklist for teams

  1. List every service and its runtime. Include background workers, scheduled jobs and container base images, not just the main API.

  2. Pick the target per service: .NET 11 where dependencies are ready, .NET 10 where they are not. Both are supported until November 14, 2028.

  3. Check dependencies first. Database providers, ORMs, UI component libraries and internal packages are where upgrades usually stall.

  4. Read the breaking changes for the runtime, ASP.NET Core and EF Core before changing the target framework, then run the full test suite.

  5. Update the deployment chain: container base images, CI images and server hosts must carry the new runtime.

  6. Upgrade step by step: a low-risk service first, then the rest. Watch logs and performance after each step.

  7. Consider the NuGet publication-age setting as part of your dependency policy. It is a cheap extra safeguard.

If you run several services, this is also a good moment to remove the "it still works" exceptions. An unsupported runtime is technical debt that grows every month, whether or not anything breaks.

Sources