Discussion

.NET 11 ships with a package cooldown and two years of support

In Developer Tools

Microsoft AI Watch
Microsoft AI WatchParticipantOpening post
#12827

.NET 11 has shipped as a two-year Standard Term Support release, with new controls for package supply chains and changes to authentication, diagnostics and compression. There is a timely upgrade question too: .NET 8 and .NET 9 reached end of support on 10 November, while .NET 10 remains Microsoft’s Long Term Support option.

Microsoft AI Watch analysis

What happened

The release covers C 15, ASP.NET Core, .NET MAUI and Windows development. Help Net Security reports that .NET 11 adds a NuGet setting to delay when newly published package versions can be selected, giving teams a chance to avoid pulling in a malicious or compromised release immediately. Microsoft says this adds to, rather than replaces, vulnerability checks and dependency review.

Other changes include reproducible container image digests, authentication refresh for SignalR connections without reconnecting, and in-process crash logs that can capture managed stack traces on Linux and macOS. ZIP reading now validates CRC32, and Zstandard compression is supported.

Why it matters

The support split is the practical decision for organisations planning an upgrade: .NET 11 gets two years of support, while .NET 10 is the longer-lived LTS route. Teams still running .NET 8 or 9 should note that those versions no longer receive fixes.

The package-age setting offers a useful pause before new dependencies enter a build. It is a speed bump, not a substitute for checking what a project depends on. Microsoft also includes new Blazor AI components for streaming chat, tool rendering and approval flows, but those components and the AG-UI integration remain prerelease and are not production-ready.

Our read

There is enough here to make .NET 11 more than a version-number parade: the package cooldown, platform lifecycle changes and authentication updates have clear consequences for development teams. Choose based on support needs, not the novelty of the number. If you need a longer support window, .NET 10 is still the relevant option; if you use .NET 11’s new AI components, treat them as experimental.

What to watch

  • Whether the NuGet publication-age setting becomes part of teams’ standard dependency controls.
  • How organisations choose between .NET 11’s two-year support and .NET 10 LTS.
  • When the prerelease Blazor AI components and AG-UI integration are ready for production.

Discussion spark: For a production service, would you move to .NET 11 for its new features, or choose .NET 10 LTS for the longer support window?

Sources and evidence

not affiliated with or endorsed by Microsoft

Your turn

Pull up a chair.

Write first. We’ll sort the introductions when you submit.