Why .NET 11 STS May Beat .NET 10 LTS
Summary
Pixel shares an overview of .NET 11 STS and .NET 10 LTS, explaining their support tracks and why both end support on November 14, 2028. The announcement covers migration trade-offs, when .NET 11 may be the better target, when .NET 10 makes more sense, and a pre-upgrade checklist.
DEV Community
.NET 11 Unpacked: Why I'm Recommending STS This Time
Table of Contents What to Expect From This Article A Short History of LTS and STS Why There Are Two Tracks at All? Why Microsoft Extended STS to 24 Months? The Catch: The Same End Date Why .NET 11 Might Be the Better Migration Target Right Now "But It's Not Battle Tested Yet" When .NET 10 Is Still the Right Call What I'd Recommend, by Situation A Pre-Upgrade Checklist Wrapping Up What to Expect From This Article For years, my advice on .NET upgrades was simple: plan around LTS releases. Skip the STS ones unless you have a very good reason. This November, that advice is not as strong as before. .NET 10 (LTS) and .NET 11 (STS) both reach end of support on November 14, 2028. Same day. One of them is a year newer. In this first article of the .NET 11 Unpacked series, I'll walk through where LTS and STS came from, why the two tracks exist, and why, for a lot of teams right now, .NET 11 may be the better upgrade target. I'll also cover when it isn't. A Short History of LTS and STS The two-track model is almost as old as .NET Core itself, which has been around since 2016. But the rules have changed several times. When What changed Nov 2026 .NET 11 ships as STS with 2 years of support, ending on the same day as .NET 10 LTS Sep 2025 STS support is extended from 18 to 24 months, starting with .NET 9 2020 to 2022 .NET 5 drops "Core" from the name, the non-LTS track gets 18 months, and it's renamed from "Current" to "Standard Term Support" 2019 Microsoft commits to a new major version every November: even numbers are LTS, odd numbers are not 2016 .NET Core 1.0 defines two release types: LTS and "Current" A few things stand out. STS never meant "Short." The official name is Standard Term Support, and Microsoft's policy page still notes that STS releases were previously known as Current releases. Most of us (me included) read the "S" as "Short" for years. That small misreading did a lot of damage to how people see these releases. STS support has only ever grown. It went from "a few months after the next release" to 18 months, and now to 24. So I guess "standard" is even more suitable wording here. By the way, LTS has stayed at three years the whole time. It hasn't changed. The 2025 change is the one that matters here. Under the old rule, an STS release was supported for 6 months after its successor shipped. Under the new rule, it's 12 months. That one change lines up the end date of every STS release with the LTS release before it. Why There Are Two Tracks at All? The two tracks serve two kinds of teams. LTS is for teams that want to upgrade as rarely as possible. STS is for teams that want new features and performance gains every single year. What the tracks don't differ in is quality standards. The .NET release policies say LTS and STS releases differ only by support duration, and that the team uses the same engineering and release processes for both, including for security, compatibility and reliability. The support policy page puts it even more plainly: the quality of all releases is the same. So an STS release isn't a beta, a preview or a "test" version of the next LTS. STS is a completely different concept. It's a full production release with a shorter warranty. Why Microsoft Extended STS to 24 Months? The 2025 extension wasn't really about STS users. It fixed a problem for LTS users (me included). More and more of .NET now ships out of band, outside the yearly release: .NET Aspire, Microsoft.Extensions.AI and the C# Dev Kit, for example. Those components sometimes need package versions from the newest yearly release. So a team that thought it was fully on LTS could pull in a few STS packages without noticing. Under the 18-month rule, those packages lost support six months before the LTS runtime they ran on. Moving STS to 24 months closed that gap: the STS packages now stay supported exactly as long as the LTS release before them. The side effect is the one this article is about. Every STS release now retires on the same day as th...

Powered by Readybot.io