topic: software-engineering
author: Crashtech Editorial
published: Nov 17, 2026 · read: 5 min
---
.NET 11 Is Here: Choose the Support Track Before You Retarget
.NET 11 launched as a two-year STS release while .NET 10 remains LTS. Map support dates, target frameworks, SDKs, images and runtime changes before upgrading.
On this page
Microsoft released .NET 11 on November 10 alongside its annual .NET conference. The most useful upgrade question is not whether the new runtime has attractive features; it is whether a service should move from .NET 10 LTS to .NET 11 STS now, and what exactly must change for that move to reach production. The support policy makes the choice unusually clear: .NET 10 and .NET 11 are both active and both currently list November 14, 2028 as end of support. Teams can evaluate .NET 11 on its merits without assuming .NET 10 is already out of runway. [1] [3]

Two supported tracks, different planning needs
.NET 11 is an STS release. Microsoft’s policy gives STS releases two years of support; LTS releases receive three years. The policy says the quality and servicing rules are the same—the difference is the length of the support window. .NET 10 remains the LTS option, while .NET 11 is the current STS release. With both currently ending November 14, 2028, the decision depends on the next lifecycle transition and the value of .NET 11 capabilities for a particular application. [3]
The November release also changed the support landscape for older deployments. Microsoft says .NET 8 and .NET 9 reached end of support on November 10, 2026. The same month’s servicing post lists security and non-security updates for .NET 8, 9 and 10 and advisories affecting .NET 11 as well. A team still running an older line should therefore distinguish “a new framework is available” from “our existing target remains supported.” Record each application’s target and hosting runtime, then map it to the support policy. [4]
This is a portfolio decision, not just a developer workstation choice. A service may compile on a new SDK but still deploy on an older runtime, use a container image with an older runtime layer, or depend on libraries that have not been validated for the new target. Conversely, an application can remain on .NET 10 while the team tests .NET 11 in a branch. Keep the chosen support track explicit rather than letting whichever SDK is installed determine it accidentally.
What .NET 11 adds
Microsoft’s launch post highlights C# 15 union types and closed hierarchies, a Native AOT CLI host, a warm MSBuild server, ASP.NET Core asynchronous validation and OpenAPI 3.2 work, .NET MAUI adopting CoreCLR as its default runtime, and library additions such as built-in Zstandard compression. The full overview covers the details and associated compatibility notes. [1] [2]
Those changes matter differently across workloads. Union types may help a codebase model a bounded set of states, but require a language and compiler upgrade plus a decision about API compatibility. A Native AOT host may reduce overhead for selected command-line applications, but AOT has different constraints than ordinary JIT deployment. A warm MSBuild server can affect developer build loops without changing service runtime behavior. ASP.NET Core validation or OpenAPI changes may be directly relevant to web applications, while .NET MAUI runtime changes target mobile projects.
Treat each feature as a candidate, not a blanket benefit. Start with the release notes for the framework area you use, then verify package support, platform requirements and any breaking changes. An application does not gain every .NET 11 improvement simply because it compiles under the latest SDK.
The upgrade is several coordinated changes
A deliberate framework move usually touches more than one file. Set the project’s TargetFramework to the intended target, review global.json so local and CI builds select the intended SDK, update package and workload versions, and inspect container base images or hosting settings. Native dependencies, publish mode, platform-specific tooling and database drivers may also need changes. Microsoft’s announcement explicitly warns that installing the SDK alone does not retarget an app. [1]
The deployment runtime is a separate concern. A build pipeline can use the .NET 11 SDK while the produced application still targets .NET 10; a server can keep running the prior process after new files arrive; a container may still use an older runtime image. For each workload, identify what compiles it, what runtime launches it and where that runtime comes from. Verify the running deployment rather than relying only on a developer’s dotnet --version.
Build a small compatibility matrix for each service: current target, candidate target, framework-dependent or self-contained deployment, operating system and architecture, native libraries, package support, and rollback method. Run unit and integration tests, then exercise the real publishing mode and container or hosting environment. Measure startup, memory use and representative request behavior if those are reasons for upgrading. A faster compiler command does not prove a production service is faster.
A practical adoption sequence
- Inventory support exposure. Find applications still targeting .NET 8 or .NET 9 and assign owners to move them to a supported line.
- Choose a track. Keep .NET 10 LTS when its stability window fits; evaluate .NET 11 STS when its capabilities or runtime updates justify the change.
- Read scoped release notes. Focus on the framework components actually used, including breaking changes and platform constraints.
- Update the full build-and-deploy chain. Set target framework and SDK selection, packages, workloads, build images, runtime images and hosting configuration intentionally.
- Validate the shipped artifact. Test with the production publish mode, native dependencies, representative data and deployment host; confirm which runtime is actually serving requests.
- Keep servicing current. Track monthly security updates and maintain an exception process for workloads that cannot move on schedule.
For a team already on .NET 10, there is no support-policy emergency to jump to .NET 11 simply because it is new. Teams on .NET 8 or .NET 9 have a more immediate lifecycle task. For either group, the same discipline applies: make the target and runtime visible, test the deployment artifact, and use the support policy as a calendar rather than a guess.
Frequently asked questions
When did .NET 11 release, and how long is it supported?
.NET 11 launched on November 10, 2026 as a Standard Term Support release. Microsoft's support policy lists November 14, 2028 as its end-of-support date.
Should every .NET 10 app move to .NET 11 now?
No. .NET 10 remains an active Long Term Support release, and Microsoft lists both .NET 10 and .NET 11 through November 14, 2028. Choose based on compatibility, feature needs and your team's servicing policy.
Does installing the .NET 11 SDK retarget an application?
No. Installing an SDK adds tooling but does not change a project's TargetFramework, global.json selection, deployment runtime, container base image or native dependencies. Update and validate those parts intentionally.
/* Comments */
Comments are offline right now — we reconnect automatically, nothing is lost.