The horrible naming thing is epitomised by the frankenstein that is, "ASP.NET Core 2.3", which is a re-release of "ASP.NET Core 2.1", which is actually a .NET Framework thing.
Re-released because ASP.NET Core 2.1 had a better support lifecycle than ASP.NET Core 2.2, and people "upgraded" to 2.2 not realising this.
So people got stuck on unsupported 2.2, rather than the supported 2.1.
So they re-released 2.1 as 2.3, to give people an "upgrade" path from 2.2 to 2.1.
All named after "ASP.NET Core" which, confusingly, is detached from ASP.NET on .NET Core.
( .NET Core which is now just ".NET" , of course. )
I swear .NET has had the best technology focus for the past 5 or so years, but has had absoultely the worse brand and a complete lack of developer relations / brand ambassador type work.
They need someone who can turn around and tell them to stop this madness, and focus on getting out that .NET is a fantastic ecosystem that performs damn well, and modern C# a pleasure to write in.
But instead we get stuff like "EF Core 9" that targets .NET 8, and all the 9.0.x system libraries, where isn't not clear whether you should be using them if you want to stick to the LTS and target .net 8.
Re-released because ASP.NET Core 2.1 had a better support lifecycle than ASP.NET Core 2.2, and people "upgraded" to 2.2 not realising this.
So people got stuck on unsupported 2.2, rather than the supported 2.1.
So they re-released 2.1 as 2.3, to give people an "upgrade" path from 2.2 to 2.1.
All named after "ASP.NET Core" which, confusingly, is detached from ASP.NET on .NET Core.
( .NET Core which is now just ".NET" , of course. )
Read the whole horror-show here: https://devblogs.microsoft.com/dotnet/servicing-release-advi...
I swear .NET has had the best technology focus for the past 5 or so years, but has had absoultely the worse brand and a complete lack of developer relations / brand ambassador type work.
They need someone who can turn around and tell them to stop this madness, and focus on getting out that .NET is a fantastic ecosystem that performs damn well, and modern C# a pleasure to write in.
But instead we get stuff like "EF Core 9" that targets .NET 8, and all the 9.0.x system libraries, where isn't not clear whether you should be using them if you want to stick to the LTS and target .net 8.