I've heard that Microsoft has officially stopped updates for .NET Framework and is focusing on .NET (formerly known as .NET Core). With this in mind, would it be a mistake to start a new application using .NET Framework? Are there any specific situations where it still makes sense to use .NET Framework, especially if a project was initially developed using it and there's no plan for migration to .NET or another platform? I'm also trying to explain this to a senior programmer who insists on continuing to build new applications in .NET Framework instead of transitioning to something like .NET Core or even exploring Python. Am I missing something here?
4 Answers
I'd suggest building a small demo app using the latest .NET version and showing it to your senior programmer. That might help illustrate the advantages of moving to the newer platform.
I'm currently stuck working on a large .NET Framework project with classic ASP.NET and tons of outdated library dependencies. Honestly, it's a nightmare. I think I’d prefer using Java over .NET because, unlike .NET, even 20-year-old Java projects can still run on the latest JDK and IDEs, making it easier to keep things updated.
Microsoft has set the end-of-life for .NET Framework 4.6.2 for January 2027, which isn't far off. While .NET Framework 4.8.1 might still have a few years left, if your plan is to build something that needs to last over 10 years, going with .NET Framework may not be wise.
You definitely shouldn't start a new project in .NET Framework. I'd recommend jumping straight into .NET 8, or even .NET 9 if you're starting today. The only time you might consider .NET Framework is if you're really tied to a legacy 3rd party library that hasn’t migrated yet, but that's pretty rare these days.
Related Questions
How To: Running Codex CLI on Windows with Azure OpenAI
Set Wordpress Featured Image Using Javascript
How To Fix PHP Random Being The Same
Why no WebP Support with Wordpress
Replace Wordpress Cron With Linux Cron
Customize Yoast Canonical URL Programmatically