Using WebAssembly to run, extend, and secure your .NET application

on YouTube ↗53m

" summary

Shows how .NET runs inside browser and servers by compiling runtimes to WASM and using WASI: Blazor downloads DLLs and a .NET WASM CLR, server-side uses wasmtime or wasmEdge to host .NET via the WASI SDK and the wasmtime .NET package. Demo copies /etc/hosts from a Rust WASM module into a .NET host, succeeds only after granting pre-open directories. Runtime enforces fuel-based CPU budgets (example: 35,000 fuel used, trap at 5,000) and binaries grow (native 145 KB vs WASM ~8.5 MB). Shows running WASM in a TEE via anox.

AI-written summary · about

" chapters (15)

1. 0:00Start
2. 2:14WebAssembly - AutoCAD
3. 2:52WebAssembly - SDK's
4. 5:10WebAssembly Design
5. 6:59WebAssembly Memory
6. 12:51Blazor WebAssembly
7. 18:48Docker vs WASM & WASI
8. 26:19Experimental WASI SDK for .NET
9. 41:05WASM - What's next?
10. 41:51Dependencies
11. 42:19Malicious module
12. 42:54Process Isolation
13. 43:33WebAssembly Nano-Process
14. 50:29Conclusion
15. 51:47Questions?

" related talks

• 55mUsing WebAssembly to run, extend, and secure your .NET applicationNiels Tanis · NDC Porto 2023
• 29mBringing WebAssembly to the .NET MainstreamSteve Sanderson · Cloud Native Wasm Day Europe 2022
• 48mWebAssembly Beyond the BrowserMete Atamel · JCON Europe 2023
• 36mWhy you should consider Web AssemblyHåkan Silfvernagel · Jfokus 2019
• 20m Running .NET code in isolation using WebAssemblyAndrei Ciobanu · dotnetdays 2023
• 50mWeb AssemblyBrian Sletten · Developer Summit 2020
• 32mBringing WebAssembly outside the web with WASILin Clark · Full Stack Fest 2019
• 42mWebAssembly beyond the browserMete Atamel · Devfest Strasbourg 2023