Developers renew push for longer Microsoft .NET LTS support as enterprise upgrade squeeze worsens

A developer has reopened a long running complaint about Microsoft's .NET long-term support policy, arguing in a new GitHub issue that the three-year free support window forces enterprises into an unsustainable upgrade cadence. The issue, filed earlier this month, revives tension between Microsoft's annual release schedule and the multiyear upgrade cycles of large organizations.

The complaint notes that half of deployed versions for one developer's software are running on .NET releases Microsoft no longer supports, according to the developer's own telemetry data.

Support window math creates a one-year upgrade crunch

Microsoft currently grants even-numbered .NET releases three years of free support and odd-numbered releases 18 months. The core problem, the developer wrote, is that when a new LTS release ships, two of the three support years for the prior LTS version have already elapsed. That leaves enterprises about one year to complete the upgrade from one supported version to the next. The developer argued that timeline is tight even for well-resourced teams and drives potential customers away from software built on approaching end-of-life releases.

Other commenters on the issue echoed the frustration. Some said they try to rely on the legacy .NET Framework, whose support is tied to the Windows lifecycle, but find that choice narrowing as libraries and frameworks drop support for the older platform. A Microsoft proposal earlier this year to drop .NET Framework support from a database library drew a developer response that the legacy framework remains the only .NET target with a support timeline that fits enterprise deployments. Microsoft closed that proposal as not planned.

Competing platforms offer longer free support

The gap extends beyond internal debate. Oracle provides five years of premier support for Java LTS releases plus optional extended support, and Python delivers five years of security fixes for every release. Microsoft's free three-year window puts .NET at a disadvantage compared with those ecosystems.

This is not the first time the issue has surfaced. A similar complaint in 2023 drew a response from Microsoft program manager Richard Lander, who said the company weighed longer support windows and paid extended support but opted to stick with only the free plan to balance stable deployment time with the team's ability to innovate.

The GitHub issue remains open. It appeared weeks after Microsoft's Build developer conference, where the company pushed AI deeper into its tooling but did not address the support lifecycle question. Enterprises that build on .NET now face a choice: accelerate migration cycles or risk running unsupported software as Microsoft's clock keeps ticking.