I've heard that Microsoft is no longer releasing updates for .NET Framework and is instead focusing on .NET 6+, which used to be known as .NET Core. I'm wondering if it's wise to learn or use .NET Framework for a brand new application. Are there any valid reasons to stick with .NET Framework, especially if the application isn't transitioning from an existing .NET Framework project? I'm having a difficult discussion with a senior developer who insists on using .NET Framework for new apps instead of upgrading to .NET Core or even exploring Python. Am I missing something important here?
4 Answers
Why not build a sample application using the latest version of .NET? That could really demonstrate the advantages of newer frameworks to your senior developer and help in the discussion.
It's definitely not advisable to start a new project in .NET Framework. Go with .NET 8 or even .NET 9 if you can! The only time I would consider .NET Framework is if you absolutely depend on a third-party library that hasn’t migrated yet. But even then, that's getting rare these days, so I wouldn't recommend it unless there's no other choice.
If you're starting today, aim for .NET 9, and if you're starting in the next few weeks, aim for .NET 10!
I’m working on a big .NET Framework project using ASP.NET Classic with a ton of outdated libraries. It's quite frustrating. If I had the choice, I'd prefer Java, where even older projects continue to work with the latest versions easily.
Microsoft has already announced the end-of-life for .NET Framework 4.6.2 is set for Jan 12, 2027. While .NET Framework 4.8.1 doesn't have an official end-of-life date, given its release in 2022, it might only last another 7 to 8 years. If you plan to build something that needs to last over 10 years, using .NET Framework probably isn't a great idea.
I’m stuck using .NET 4.7.2 at work because that's all our machines support. It definitely limits us, and I would never choose it for new projects.