Lightning Talk: Implementing Wasm Debugging with .net in vscode
summary
Implements .NET Wasm debugging in VS Code by translating Chrome DevTools Protocol messages into the runtime’s Soft Debugger Protocol via a CDP proxy, enabling breakpoints, locals and call stack inspection for browser (wasmi) and standalone (Wazi) runs. Browser mode uses runtime.evaluate plus injected debugger statements to signal the proxy; Wazi reuses a preopened socket and a single-threaded communication loop. Experimental Firefox support exists and a recent PR adds multi‑thread runtime adjustments; demos show breakpoints, variable views and resume working end‑to‑end.
AI-written summary · about
chapters (7)
- 0:00Start
- 0:55Why had we decided to use Chrome DevTools Protocol?
- 5:48Multithreaded environment
- 6:53Why it was fast to implement?
- 7:30What was the challenges?
- 8:36Debugging the C# app on VsCode
- 9:03VsCode Configuration for debugging on Wasm and on Wasi
related talks
24mNo More Printf: Interactive Debugging Wasm for web and server
26mNavigating Strategies for Debugging WASM
09mDebugging WebAssembly with modern tools
46mWebAssembly (Digging a bit deeper)
13mWebAssembly Debugging Demystified
53mUsing WebAssembly to run, extend, and secure your .NET application
29mBringing WebAssembly to the .NET Mainstream
51mImplementing a WASI Host for Visual Studio Code
