Microsoft calls time on ASP.NET Core 2.3 on .NET Framework

April 8, 2026
A hand dialing a phone on a wooden desk. Office environment with keyboard and planner.
Photo by RDNE Stock project on Pexels

The sun sets on a compatibility hack

Microsoft has announced an end-of-support date of April 7, 2027 for ASP.NET Core 2.3, the oddball release that let newer ASP.NET Core code run on the Windows-only .NET Framework. Daniel Roth, a principal product manager, said "after that date, Microsoft will no longer provide security patches, bug fixes, or technical support for ASP.NET Core 2.3," and users are being nudged toward modern ASP.NET on .NET 10. It has been reported that Microsoft defends the move by calling 2.3 a "tool" rather than a library, which — conveniently — carries a shorter lifecycle requirement.

Why developers are bristling

This feels less like tidy housekeeping and more like a sore spot reopened for teams stuck on older Windows Servers. It has been reported that 2.3 was itself a re-release of the 2.1 LTS codebase created to sidestep the breaking changes in 2.2, and many shops leaned on that awkward compromise. One user allegedly called the version bump "a massive problem for us" because code added in 2.2 disappeared in 2.3, breaking assumptions — and expectations set by semantic versioning. Who ends up paying the fiddly migration bill? Hint: not Microsoft.

The numbers and the pitch

NuGet statistics show both 2.2 and 2.3 remain in widespread use, so this sunset will touch a lot of running systems. Roth told users the ongoing maintenance and compliance cost "pulls resources from investment in our modern .NET platform," and suggested migration tools — including AI-assisted tools — as the way forward. It has been reported that some developers feel Microsoft is exploiting a tooling loophole to shorten support; others, weary and pragmatic, are already charting upgrade paths to .NET 10 or planning rollbacks and rewrites.

So what now?

Short answer: plan to move. Longer answer: inventory your apps, estimate the migration pain, and factor in time to rework any 2.2-dependent behavior that 2.3 deleted. The industry is moving fast — cloud-first, cross-platform, AI-assisted — and Microsoft is clearly trying to push the fleet in one direction. For teams still clinging to legacy Windows servers, that shove will sting.

Sources: The Register