Comment by to11mtm
3 months ago
I get you actually.
MVC churn was real, EF Churn was real, heck NETCORE itself was a (at least warned about) churn, 3.1->6.0 was minor but still definitely a thing [0].
[0] - Now that I'm thinking it out loud, maybe that's why they changed the branding from .NET CORE to just .NET; The churn was more or less 'done'...
I'm only now deprecating a netcore 2.2 API that used a 4.8 framework domain/repository layer. At the time it seems like a good idea and it received automatic security patches.