.NET Rocks! · Carl Franklin

ASP.NET Core in 2026 with Daniel Roth

April 2, 2026·1 hr·5 clips
Carl and Richard ask listeners to share their Y2K stories and how .NET shaped their careers for episodes 1999 and 2000.
Daniel Roth is here. Carl Franklin and Richard Campbell clear the patron note, then the Episode 1999 and 2000 calls for listener stories, and the show moves into ASP.NET Core platform work. Blazor gets a real chunk of the conversation. Roth says runtime async is a big effort for 11, while the full version of that story probably lands after 11. WebAssembly is the other long road. The current WebAssembly runtime for .NET comes from the old Mono code base, and the team wants to move it toward a CoreCLR-based runtime. That is not a little cleanup job. Roth puts it inside a wider runtime consolidation push, with mobile workloads already moving that way and WebAssembly coming later. Carl and Richard catch the point right away: this matters to ASP.NET Core and Blazor, not just some runtime side alley. Then Richard asks whether the ASP.NET Core team pushes for language changes. Roth gives the easy yes. Minimal APIs are the example, with compiler collaboration, language features, source generation, and infrastructure all aimed at making the model feel better to use. Razor sits close by. Roth says Razor compilation is one place where ASP.NET Core scenarios shaped work across the stack. The useful bit is the closeness. Roth describes a steady loop across runtime, frameworks, libraries, languages, app models, tooling, and the developer-facing pieces that keep ASP.NET Core from feeling clumsy. It is an internal view, sure, but the takeaway is plain: Blazor, Minimal APIs, and Razor do not come from one team tossing code over a wall. The close is quick. Carl thanks Dan, the agentic UI thread stays open for next time, and the show signs off with the old ritual: now go write some code.

As heard by us

A clear look at how ASP.NET Core stays tied into the wider .NET stack.

ASP.NET Core comes across as one part of the .NET stack, not a standalone web framework. Daniel Roth walks through runtime async work landing in .NET 11, the push to bring the WebAssembly runtime toward CoreCLR, and the constant handoff between ASP.NET, C#, language features,…

Read the full review in PlayNext →

Why you'd press play

Press play if you want the .NET roadmap talk from the inside.

Read the full recommendation in PlayNext →
Listen to the show on