Skip to main content
Official Microsoft metadata

.NET release support and upgrade planning

Use current SDK, runtime and lifecycle data to choose a supported release channel, plan upgrades and verify what your build agents should install.

Default for most production apps

Choose an active LTS channel when you value a longer support window and a predictable major-version cadence.

When an STS channel fits

Choose supported STS only when your team can plan the next major upgrade on its shorter lifecycle and needs the newer platform features.

Before adopting a preview

Validate CI images, package compatibility, deployment targets and a rollback plan. Preview status is not a production-support promise.

Channels to evaluate now

Start with the release type and support window, then open the channel page for exact SDK and runtime values.

3 supported channels listed

.NET

.NET 10.0

LTS
SupportedSecurity update
Latest SDK
10.0.302
Runtime
10.0.10
Support
Nov 14, 2028842 days remaining

.NET

.NET 9.0

STS
MaintenanceSecurity update
Latest SDK
9.0.316
Runtime
9.0.18
Support
Nov 10, 2026107 days remaining

.NET

.NET 11.0

STS
Preview
Latest SDK
11.0.100-preview.6.26359.118
Runtime
11.0.0-preview.6.26359.118
Support
Not scheduledNo published end date

Upgrade planning checklist

  1. 1. Pin the SDK deliberately. Use global.json when your solution or CI must use a specific SDK feature band.
  2. 2. Update CI and local tooling together. Compare dotnet --info output from a build agent and a developer machine.
  3. 3. Restore and test every target. Framework and package resolution can differ across multi-targeted projects.
  4. 4. Schedule before end of support. Track the published EOL date as a delivery constraint, not as a last-minute upgrade task.

Data, refresh and limits

Source: Microsoft .NET release index. Server refresh: Jul 26, 2026; cached for one hour. Limit: the index does not prove package compatibility, OS support for your deployment, or that an application is ready for a runtime upgrade.