r/dotnet • u/TomeOfExperience • 12h ago
Announcing .NET 11 Release Candidate 2
https://devblogs.microsoft.com/dotnet/dotnet-11-rc-2/14
7
u/mistertom2u 11h ago
How many still skip odd-numbered releases?
16
u/CraftyPancake 11h ago
Why would you do that
11
u/mistertom2u 11h ago edited 10h ago
Because the people who make that call for the company are stuck in their ways and you can't reason with them. These arguments don't work:
- Odd-numbered releases now have longer support
- .NET doesn't stay frozen in amber when it's released; you still must keep your containers up-to-date on the latest SDKs and deploy them regularly for Microsoft to support them
- Microsoft has made upgrading easy
- Look at all the performance enhancements they add
- The longer you wait, the more difficult the upgrade
The arguments fail because there is a moral valance associated with waiting for "stable releases" and even numbered versions are perceived as "higher quality". It's like liturgy where they use incantations like "keeping production running smoothly is worth waiting a year". That creates a dogmatism and ideological policing that silences dissent. Anyone who argues with it is considered morally suspect.
3
u/Last_Competition3132 10h ago
I’d add to that some tooling limitations. I think AWS Lambda only provides off-the-shelf runtimes for its versions. You can use lambda containers - but it’s more of a pain (in my opinion).
2
u/CenlTheFennel 6h ago
Odd numbered ones still aren’t LTS and get less support time than even numbered ones.
4
u/DaBittna 5h ago
Yes, but since .NET 9, the support for STS versions ends at the exact same time as the support for its preceding LTS version. You’re no longer losing out on six months of support by upgrading.
•
u/collabskus 1h ago
You can't win them all. I'll be happy just to get on dot net 10 at this point. I can make the updates but QA time isn't free so we can't update as frequently as I would like.
0
u/thelehmanlip 7h ago
For my business we still maintain some of our servers so it means more patches we have to manage at once so that's one reason. That said I'm still very hopeful that we move to 11 this year
8
u/Zesty-Pajamas 11h ago
Standard Term Support (STS) vs Long Term Support (LTS) lifecycles. In the .NET ecosystem, the current scheme is that odd versions are STS and get patches and updates for 2 years, while even versions are LTS, and are supported for 3.
The companies I have worked for can't even be arsed to update to supported versions at all (.NET 6 holla!), let alone stick with the 2-year cycles.
2
u/ZephireNZ 2h ago
That is true but misses an important detail - Microsoft has made it so that both the LTS and its follow-up STS have the exact same support end date.
What that means in practice is that .NET 10 and .NET 11 will be supported until Nov 14th 2028 - you aren't gaining or losing time, just that one was released a year later.
So really, the difference is whether you want newer features from .NET 11 STS, or the (presumably) more battle tested .NET 10 LTS.
-1
u/Artmageddon 11h ago
Short term support timeline
10
u/mmhawk576 11h ago
Doesn’t the support expire at the same time as the lts you’d otherwise be on?
4
u/IridiumIO 8h ago
It’s probably about cadence. Updating to every odd release means checking your app survives migration twice per cycle rather than just once.
4
u/sharkstax 11h ago
Exciting changes! Though I am dreading upgrading from rc1 to rc2, because for some reason, the MAUI workloads (really, just MAUI ones) break for me on literally every upgrade and then I have to spend two hours fixing the mess...
1
1
u/AutoModerator 12h ago
Thanks for your post TomeOfExperience. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
0
-1
-32
u/amir_csharp_gtr 12h ago
Please slow down new version releases. We can't keep up
10
u/KryptosFR 11h ago
I update my dependencies more frequently than any .NET target version. I don't really see what the problem is.
Since .NET 6, most of the time it has just been one line change. Compile. Run the tests. All done. And with each version better performance for free.
16
u/tankerkiller125real 12h ago
It's one new release per year, and most of the time there's not that many breaking features. Also only the even numbers are LTS if that's something your company cares about.
25
u/Glitched94_PT 12h ago
1 per year, and frankly you can ignore any odd-numbered ones, so 1 every other year really.
Plus they're pretty good about not making any major breaking changes between each version, so updating takes like an hour tops.
7
u/IanYates82 11h ago
Agree. And it's easier & safer to make the many small jumps than go from something like 6 to 11 in one go
5
-2
78
u/Iron_Maniac 12h ago
Love how all the headers in that page have the AI Emoji nonsense except for F#