.NET Rocks! Razor Tooling in Visual Studio 2026 with David Wengier
Sep 18, 2025
David Wengier, a principal software engineer at Microsoft, leads the Razor tooling experience for Visual Studio and VS Code. In this chat, he reveals the exciting co-hosting model with Roslyn that turbocharges Razor performance and reliability. David dives into the shared capabilities between Visual Studio and VS Code, enhancing developer tools through the Language Service Protocol. He also shares upcoming improvements in Visual Studio 2026, including faster Hot Reload and bug-fixing guidance, making for a more seamless coding experience.
AI Snips
Chapters
Transcript
Episode notes
LSP Brought Portability But Missed .NET Concepts
- Razor tooling originally used LSP to share language features between VS Code and Visual Studio.
- That worked well for portability but exposed mismatches because LSP lacks native .NET project concepts.
Duplication Caused Sync Bugs and Fragile Caches
- Razor and Roslyn duplicated project and file monitoring which caused synchronization issues.
- That duplication led to bugs and stale caches that impacted editor reliability.
Co-Hosting Replaces LSP Calls With Direct Roslyn Access
- Co-hosting means Razor tooling shares the same view of the world as Roslyn rather than communicating via LSP strings.
- That enables direct API calls into Roslyn for faster, more reliable results and less serialization overhead.