Breaking changes in AspNet Core between 8 and 10. Happens for Duende Identity Server every time, though they have been good about dropping same day or close to it and even pre-releases against preview/rc.
I haven't had issues with CLR updates in a while. That seems to have stablized from .Net 6 , though you still release quite a few breaking changes there too. Luckly, not in any APIs I was using. For the systems I've been dealing with, it's always a breaking change in AspNet Core, EF Core, or Extensions, or a breaking change in the platform somewhere that requires a dependency to update their code.
And like I said, waiting on EF Core providers. Unfortunately, Oracle could care less if they support .Net.
I'd like to say this is a one off, but Since 1.0 I've managed 40 products. 1.1->2.1 💥, 2.1->3.1 💥, 3.1->6.0 💥, 6.0->8.0 💥, 8.0->10.0 💥. Every one required code changes and/or dependencies to become compatible (either waiting, forking, or contributing back). I never had the luxury of just changing the moniker, compiling, and calling it a day.
.Net upgrades in the realworld are a major upgrade, require code changes, dependency upgrades, full regression testing cycles including SAST, DAST, and PEN, and in the EU, filed reports to the EU with the results of said testing. That doesn't all happen in a few days. That is months worth of planning and work, scheduling with Red Teams, etc.
I know the breaking changes are the trade-off of moving fast and innovation. I don't mind that part. Infact I think it's awesome. The problem is the 3yrs. Especially the 1 year between release and EOS of the previous. It's not enough time for many industries to update and remain compliant.
You wouldn't dream of making Windows Server or SQL Server support cycles 3 years and only giving 1 year to uograde. So as an ISV, why does my software have to go out of support in a year? How am I supposed to release even once a year and have any kind of realistic enterprise software support with my customers?
If there is a way for Sales to hit their numbers every quarter and not have customers in perpetual upgrade mode and provide realistic enterprise level support cycles (without HeroDevs), I'd love to hear it. I'm happy to brainstorm on this.