What to Expect from .NET Conf 2020: The Great Unification

Mark your calendars: .NET Conf 2020 runs November 10-12, and it’s free and virtual again this year. This is the one Microsoft has been building toward for a while now, since it’s expected to be the launch event for .NET 5.0 — the release that finally merges .NET Framework and .NET Core into a single, unified platform.

If you haven’t been following the .NET naming saga, here’s the short version. For years Microsoft ran two parallel tracks: the old, Windows-only .NET Framework, and .NET Core, the newer cross-platform rewrite. Having two things called “.NET” that weren’t fully compatible was confusing for newcomers and annoying for teams trying to figure out which one to bet on. The plan has been to collapse them into one thing, and that thing is .NET 5. Notice there’s no “.NET Core 4” — they skipped straight to 5 partly just to avoid version-number confusion with Framework’s 4.x line.

What’s actually shipping

Assuming the conference timeline holds, .NET 5.0 final should be the headline release. Alongside it, C# 9 is expected to land with a handful of features that C# developers have wanted for a while:

• Records — a new reference type built for immutable data, with built-in value-based equality so you don’t have to hand-roll Equals and GetHashCode for simple data-holder classes.
• Init-only setters — properties that can be set during object initialization but become read-only afterward, giving you immutability without needing a full constructor for every property.
• Pattern-matching improvements — more expressive switch and type-check syntax, building on what C# 8 already started.

F# 5 is also expected at the show, continuing Microsoft’s habit of treating F# as a first-class citizen in the .NET family rather than a side project.

Why unification actually matters

It’s easy to shrug this off as internal plumbing, but the practical effect is real. Right now, if you’re starting a new project, you have to make a call about which .NET flavor to target, and that decision has downstream consequences for what NuGet packages work, what platforms you can deploy to, and how long-term support looks. Once .NET 5 is the only .NET, that decision mostly goes away. One SDK, one set of APIs, and it runs on Windows, Linux, and macOS.

That’s a bigger deal for enterprise shops than it might sound. A lot of companies have been sitting on .NET Framework because rewriting for Core felt like a project unto itself, even though Core has had better performance and cross-platform support for years. A unified release removes the “which train do I get on” anxiety and gives everyone a single, obvious upgrade path going forward.

I’d expect the conference sessions to lean heavily into migration guidance — how to move existing Framework apps forward, what breaking changes to watch for, and probably some ASP.NET and Blazor performance talks given how much work has gone into that stack. If you’re a .NET developer, or even just curious where Microsoft’s language design is headed, it’s worth tuning into at least the keynote. I’ll be watching for how much of the “unification” messaging is marketing versus how ready the migration tooling actually is in practice.