Hacker News Reader

.NET LTS is on a 2-year cycle, isn't it?

I've worked in .NET shops with very niche WPF/WinForms applications where customers were years behind with our software/major .NET Framework releases.

I don't think it's a technical challenge, more a cultural one.

View on HN

A shift in those cultural dynamics is that you can ship the current .NET LTS with your app (or even STS if you feel like making that sort of security support SLA with your own clients). You aren't relying on their Windows Update habits (or lack of them) or having to install a big .NET installer that might break their other apps.

They may still get left behind on an older version of your software because they want to be, but their relationship to Windows is no longer the big excuse/reason to skip updating to your latest that it used to be.

You are right that it’s on a 2 year cycle. Though there is support for 3 years, so you could safely put off an upgrade for up to a year if there are breaking changes one release.

Reply on news.ycombinator.com