.NET 5 and Windows 10 20H2 drop out of support

Microsoft has pulled the plug on support for .NET 5 and the Pro and Home versions of Windows 10 20H2. .NET 5 is not to be confused with the venerable .NET Framework, which will linger on until its parent OS breathes its last. .NET Framework 3.51 SP1, for example, will carry on until the beginning of 2029 – over 20 years since …

[Anonymous Coward]

When a 3 year life is defined as LTS, half the projects adopting NET6 won't even have left testing before EOL.

Good way to ensure money printing consultancy on endless updates. Bad way to encourage repeat business.

Thankfully choice does exist. Make use of that power lest you lose it.

[James Anderson]

Newish hardware rendered obsolete

Low end laptops and celerion based “sticks” purchased as late as 2021 are now obsolete.

Bill Gates no longer runs the company, but is busy saving the planet. Perhaps he could have a word with the current management who are consigning millions of perfectly good machines to landfill.

[SNaidamast]

Constant churning of technology releases is getting ridiculous!

I am a senior software engineer developing ongoing extensions to a new product I have just released.

I work in Visual Studio 2019 and have worked with .NET since it was first commercially released in 2001.

Since the advent of Microsoft's move to ASP.NET MVC in 2010, the company has been churning out technology releases and upgrades\updates at such a reckless speed that no one can no longer keep up with such technologies. And there is a lot of dissatisfaction in the Technical Community regarding this. And we call all see this with large increase in software defects making it into the public domain for use by end-users.

I recently tried to upgrade to the recently released Visual Studio 2022 (which has support for .NET 6.0) and it completely messed up my Visual Studio 2019 installation (which has been a reported issue) so that I had uninstall both and reinstall Visual Studio 2019 so I could get my commercial product back into the development environment.

I did this upgrade so I could recompile a number of data access layers I had written to the .NET 6.0 Core Platform. However, there is little wrong with the .NET 5.0 platform that I could see as it supported the type of web development I was learning (Blazor in a WebForms-like manner).

But I can't currently use .NET 6.0 because Visual Studio 2022 is currently too unstable for me to work with right now. However, we have .NET 7.0 Core right around the corner.

Its not only the machinery that is being made obsolete its also that developers and engineers simply cannot keep up any longer with these platform upgrades with features that are for the most part meaningless in the scope of real-world development or end-user usage.

I have been considering simply dropping the Microsoft development environments by purchasing RemObjects latest product, Mercury Visual Basic, which supports everything in the older and newer frameworks. Tracking RemObjects Software for a while, they don't seem to constantly churn out releases on such an ungodly schedule.

Has anyone ever asked Microsoft why the need for so many upgrades outside of making money?

[Anonymous Coward]

Re: Constant churning of technology releases is getting ridiculous!

On environment churn, I and a development outfit I use for outsourcing use VM's to deal with dependency hell.

One VM per project; and you can snapshot both application and development environment in time to go back to should it be required.

Doing this in bare metal is just a nightmare.

[DomDF]

LTS

How long do Windows versions get support for? My Ubuntu 18.04 install still has another year of support left, and predates 20H2 by two years.

Perhaps this should be classed as "Medium Term Support" ?