.NET 5 Nears Launch: Microsoft's Plan to Unify .NET

If you’ve written code against more than one flavor of .NET over the years, you know the mess Microsoft has slowly backed itself into. There’s the old .NET Framework, still humming along in countless enterprise apps and basically frozen in amber on Windows. There’s .NET Core, the cross-platform rewrite that’s become the default for new server-side work. And there’s Xamarin, the mobile-focused branch that never quite got the same love or tooling parity. Three ecosystems, three sets of APIs to remember, three sets of quirks to explain to new hires. .NET 5 is Microsoft’s attempt to finally stop apologizing for that and just fix it.

The pitch is simple: one .NET. Preview 8 shipped last month, and Microsoft has been public and consistent about the target date — general availability on November 10, 2020, timed to land alongside .NET Conf. That’s a real date on a real calendar, not a vague “later this year,” which is worth noting given how often platform unification efforts drift.

Why “5” and not “4”

The naming itself tells you what’s going on. Microsoft skipped .NET Core 4 entirely to avoid confusion with the old .NET Framework 4.x line, jumping straight to .NET 5. It’s a small thing, but it signals the intent clearly: this isn’t “Core, but newer.” It’s meant to be the one .NET going forward, full stop. .NET Framework isn’t going away overnight — there’s too much legacy Windows software depending on it — but it’s effectively being frozen for new feature work while .NET 5 becomes the actual path forward.

Folding Xamarin in is arguably the more interesting move. Mobile development at Microsoft has always felt like a slightly separate universe from the main .NET story, with its own release cadence and its own quirks around iOS/Android tooling. Bringing it under the same umbrella means, in theory, that a C# developer’s skills and libraries transfer more cleanly between building a web API, a desktop app, and a mobile app. Whether that promise holds up in practice once real production apps start hitting it is the thing to watch.

For anyone maintaining older .NET Framework apps, the practical question is migration effort — how much of that codebase moves cleanly and how much needs surgery. Microsoft’s messaging has been that .NET Core’s compatibility work over the last few versions has closed most of the gap, but preview software is preview software, and the difference between “compiles” and “behaves identically in production” is where these things tend to get interesting.

With GA roughly two months out, September and October are going to be crunch time for anyone planning to target 5.0 at launch. Preview 8 is stable enough to poke at now if you want a head start, and given the firm November date, I wouldn’t expect a lot of slippage in scope between now and release. Worth keeping an eye on the release notes as later previews land — that’s usually where the real story of what shipped versus what got punted becomes clear.