.NET's Long-Term Support Is Not Long-Term Enough, Dev Complains

Microsoft's three-year .NET support window is too short for enterprises, developers say

A developer has reopened a long-standing complaint about Microsoft’s support policy for its .NET development platform, arguing in a new GitHub issue that the three-year window for long-term support releases is too short for enterprise upgrade cycles. The current release model gives even-numbered versions three years of free support and odd-numbered versions 18 months. The […] This story continues at The Next Web

.NET's long-term support is not long-term enough, dev complains

Microsoft's support policy for its .NET runtime and development platform is too short for enterprises, according to a developer who has revived a long-standing complaint in a new GitHub issue. The current release lifecycle for modern .NET, formerly known as .NET Core, is an annual major release, with even-numbered versions being long-term support (LTS) for three years, and odd-numbered versions maintained for two years. The legacy and Windows-on…

"Three years of LTS support for .NET is too short"

According to developers, the current .NET lifecycle does not align sufficiently with the upgrade cycles of large organizations.