Developers have expressed that Microsoft's three-year support period for .NET is insufficient for enterprises.
TL;DR Developers express dissatisfaction with .NET’s three-year LTS support, noting that many deployed versions are unsupported, while Java offers five years or more. A developer has reopened an ongoing concern regarding Microsoft’s support policy for the .NET platform, stating that the three-year duration for long-term support (LTS) releases is inadequate for enterprise upgrade cycles. The current model allocates three years of free support for even-numbered versions and 18 months for odd-numbered versions. Meanwhile, the legacy .NET Framework, linked to Windows and offering longer support, is increasingly being neglected by the wider ecosystem.
The primary issue, as described in a recent GitHub issue, is that by the time a new LTS release is launched, two of the three years of support for the previous version have already passed. This effectively gives enterprises about one year for upgrades, a timeframe that feels tight even for well-resourced teams. The developer also mentioned that potential customers hesitate to adopt software nearing its end-of-life date.
Another developer noted that telemetry indicated around 50 percent of the deployed versions of their software were using versions no longer supported by Microsoft. They mentioned an effort to utilize the legacy .NET Framework wherever feasible, given its support aligns with the Windows lifecycle, though this is becoming increasingly difficult as libraries and frameworks discontinue support for it.
This complaint is not new. A similar issue in 2023 prompted a response from Microsoft program manager Richard Lander, who explained that the company designed its support timelines to balance stable deployment periods with the team’s capacity for innovation. He mentioned that discussions about longer support periods and paid extended support had occurred but that the decision was made to stick with the free model.
Microsoft's free support period is notably shorter than that of some competing platforms. For instance, Oracle offers five years of premier support for Java LTS releases and additional extended support, while Python provides five years of security updates for each release. This discrepancy has become a recurring issue for enterprises relying on .NET while working within upgrade cycles that don’t align with Microsoft’s annual release schedule.
Tension resurfaced in March when a Microsoft engineer suggested eliminating legacy .NET Framework support from a database library. A developer replied that the legacy framework and its compatibility layer are currently the only .NET options with suitable support timelines for enterprise deployments. This proposal was ultimately closed as not planned, indicating that the older platform’s longer support lifecycle is still significant for many users.
The central question remains whether Microsoft’s initiative to pivot towards speed and AI can harmonize with enterprise needs for extended platform stability. This complaint arose weeks after the company’s Build developer conference, where Microsoft integrated AI more deeply into its developer tools but did not address the support-lifecycle issue. The GitHub issue remains unresolved.
Other articles
Developers have expressed that Microsoft's three-year support period for .NET is insufficient for enterprises.
A GitHub issue contends that Microsoft's .NET LTS support duration is insufficient for enterprise upgrade cycles, resulting in half of the deployments operating on unsupported versions.
