4 ms·
> Sure, if you're developing a SaaS you can stay on top of .NET versions but it's definitely causing friction for enterprise and slow moving regulated software.
by simplotek 4y ago
> Sure, if you're developing a SaaS you can stay on top of .NET versions but it's definitely causing friction for enterprise and slow moving regulated software.
You have a point, but I'd call out that migrating to newer releases can and often is trouble-free.
A couple of months ago I worked on a .NET Core 2 web service that was put on cold storage for a few years, and all it took to migrate it to .NET Core 6 was a few version number bumps and a rebuilding the project.
YMMV of course, but LTS shelf life might not be a deal breaker.
- to11mtm 4y agoYou may have gotten particularly lucky. I say particularly, because Core2->Core3.1 was a fairly painful change for some. I'd say the 66% worst case is 'you also have to add some compat flags and stories to properly resolve the compat flags'.
- TrueSlacker0 4y agoAnd web forms to core was/is terrible.
- AlfeG 4y agoIt took almost two years of development to do this conversions in out project... but in my case heavy lift of move from webforms to mvc were already done, so it a bit easier.