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 legacy .NET Framework, which is tied to Windows and supported for much longer, is increasingly abandoned by the broader ecosystem.

The core problem, as described in the issue opened earlier this month, is that when a new LTS release arrives, two of the three years on the previous one have already elapsed. That leaves enterprises roughly one year to complete the upgrade, a timeline that is fast even for well-resourced teams. The developer also noted that potential customers are reluctant to adopt software that is already approaching its end-of-life date.

Another developer commenting on the issue said telemetry showed about 50 percent of deployed versions of their software were running on versions Microsoft no longer supports. They added that they try to use the legacy .NET Framework wherever possible because its support is tied to the Windows lifecycle, but that is getting harder as libraries and frameworks drop support for it.

The 💜 of EU tech

The latest rumblings from the EU tech scene, a story from our wise ol’ founder Boris, and some questionable AI art. It’s free, every week, in your inbox. Sign up now!

The complaint is not new. A similar issue in 2023 drew a response from Microsoft program manager Richard Lander, who said the company chose its support windows to balance stable deployment time with the team’s ability to innovate. He said Microsoft had discussed longer support periods and paid extended support but opted to continue with only the free plan.

Microsoft’s free support window is shorter than what some competing platforms offer. Oracle provides five years of premier support for Java LTS releases plus additional extended support, and Python receives five years of security fixes for every release. The gap has become a recurring source of friction for enterprises that build on .NET but operate on upgrade cycles that do not match Microsoft’s annual release cadence.

The tension was visible again in March, when a Microsoft engineer proposed dropping legacy .NET Framework support from a database library. A developer responded that the legacy framework and its compatibility layer are currently the only .NET targets with support timelines that work for enterprise deployments. The proposal was closed as not planned, an acknowledgment that the older platform’s longer support lifecycle still matters to a significant part of the user base.

The underlying question is whether Microsoft’s push to restructure around speed and AI can coexist with enterprise demands for longer platform stability guarantees. The complaint surfaced weeks after the company’s Build developer conference, where it pushed AI deeper into its developer tools but did not address the support-lifecycle gap. The GitHub issue remains open.