> .NET 11 is a Standard Term Support (STS) release with two years of support under the .NET support policy. STS and Long Term Support (LTS) releases have the same quality and servicing policies; the difference is the length of support. .NET 10 remains a supported LTS option. Stay current with servicing updates whichever release you choose.
They burried the lede on this one.
- .NET 10 is end of life'd on Nov 14th, 2028 - .NET 11 is end of life'd on Nov 9th, 2028
Which means anyone who upgrades to 11 has fewer days of support. But the idea is that you'll upgrade to 12 as soon as it's RTM'd.
The problem with that is I have clients who refuse to budge from 2.1 (or even upgrade to the 2.1 re-release: 2.3).
> The problem with that is I have clients who refuse to budge from 2.1 (or even upgrade to the 2.1 re-release: 2.3).
2.3 on .NET Framework reaches end of life on 2027-04-13, so upgrades have to happen soon.
If you mean ASP.NET Core 2.1 or ASP.NET Core 2.3, then they are actually .NET Framework despite the name, and are not the same lineage as .NET 10 and .NET 11.
It's still in support, and led to one of the most confusing release announcements in history: https://devblogs.microsoft.com/dotnet/servicing-release-advi...
ASP.NET Core 2.3 does go end of life in April 2027 however: https://devblogs.microsoft.com/dotnet/aspnet-core-2-3-end-of...
>They burried the lede on this one.
Not really for any groups that commonly use .Net. Even numbers are LTS and odd numbers are not, or at least it's been this way for a while.
>I have clients who refuse to budge from 2.1
Give me their names, sounds like it would be easy to penetrate them again and again and again with AI.
Nothing new to comment on here. MS has been open about its long term and short term releases based on even and odd numbers. Unsurprisingly, there's a web page that explains it https://dotnet.microsoft.com/en-us/platform/support/policy