Not according to MS. The say it’s supported as long as the Windows it’s on is supported, and they’re not dropping it from the next version of Windows. No new dev. But that’s fine. According to our folks Core is so stripped down we’d just wind up dropping .Net entirely. We’ll see.
It SHOULDN’T cause job loss. But it all depends on your company. My company openly resents having employees. I really gotta get out of this place.
” According to our folks Core is so stripped down”
A few years ago, I converted a 5+ million line, 400 project system from 4.8 Framework to .Net 6 and lately to .Net 10. I would say Core is far more mature than 4.8. Not trying to argue, but I was skeptical a few years ago converting to .Net 6 and thought the rewrite would be a killer being a time vampire that is usually expected with such conversions, but it turned out to be the best decision and unlocked many needed and up to date capabilities.
It was also very easy to understand the path from 4.8 to Core. As Laz said, even AI can do the conversion automagically now too. Laz is not kidding there.
The mapping from 4.8 Framework to Core Razor pages on the website code was very easy to understand and accomplish, so I can see how AI could do it with little problem.
Also, the amount of code needed for Core is much less than with 4.8 Framework. With the latest C#, the code can easily be shrunk 5:1 over previous language versions. There has been excellent updates to Core and C#.
Just my two cents.