Hidden Difficulties Implementing a Debugger for .NET WASM Apps
summary
Covers the challenges of implementing debugging infrastructure and an IDE debugger interface for .NET WebAssembly (Blazor WASM) apps, explaining issues that arise from the platform’s unique runtime environment. Focuses on concrete debugging-infrastructure problems encountered when building support for .NET WASM in IDEs.
AI-written summary · about
chapters (16)
- 0:00Introduction
- 1:31Goals and structure
- 2:33History of .NET WASM
- 5:26.NET WASM app types
- 9:27Anatomy of .NET WASM
- 14:05Debugging .NET apps
- 14:50Debugging .NET WASM
- 16:35Debug Proxy architecture
- 18:44CDP protocol role
- 23:27CDP implementation challenges
- 26:22CDP transport layer
- 28:30Rider CDP implementation
- 32:08Breakpoints in WASM
- 33:33Hot Reload in WASM
- 36:24Summary
- 37:06Q&A
related talks
56mHidden Difficulties of Debugger Implementation for .NET WASM Apps
29mBringing WebAssembly to the .NET Mainstream
53mWebAssembly Using C# Blazor
28mNorDevCon2020 Day 1 - Part 3 - Mark Flanagan
58mIntro to Blazor, WebAssembly and Razor in .Net
15mWhat is this Blazor thing, anyway?
01h 01mWhat’s next for Blazor, and .NET on WASI
33mC# and Wasm Interface Types: Hands Across the C
