3 ms·
> the thing you wrote last year doesn't look anything structurally like what you're doing now... all the 6-month-old on-line docs and tutorials aren't only use
by SideburnsOfDoom 1y ago
> the thing you wrote last year doesn't look anything structurally like what you're doing now... all the 6-month-old on-line docs and tutorials aren't only useless, but time wasting.
This is indeed a complete exaggeration.
- ourmandave 1y agoSorry, I love .NET and have used it from it's rollout back in 2002. I'm just fondly remembering the ASP.NET MVC churn or more recently, Azure API whiplash.
- SideburnsOfDoom 1y agoOnline forums often have people asking "hey I found this tutorial for learning c# but it's way way back for .NET 7 will it even work in .NET 9?" The answer is always a variation of "yes, you'll be fine, but also look at a "what's new" summary for the new version.
- to11mtm 1y agoI 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'...
- mycall 1y agoI'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.