Menu

Decompiling a Blazor WebAssembly App: Reading the .NET DLLs the Browser Downloaded
📰

Decompiling a Blazor WebAssembly App: Reading the .NET DLLs the Browser Downloaded

DEV Community: dotnet·Zero Heartbeat·5 days ago
#VT6UWsdN
#devtodotnet#devto#dev#readable#blazor
Reading 0:00
15s threshold

The first time someone opens the browser dev tools on a Blazor WebAssembly app and sees a _framework folder full of .wasm files, it looks reassuringly opaque — like the compiled WebAssembly blob you cannot read. It is not. Blazor WebAssembly does not compile your C# to WebAssembly; it ships a .NET runtime (as WASM) plus your ordinary .NET assemblies , and runs them in the browser. Those assemblies are downloaded to every visitor, metadata and IL intact, which means your client-side C# decompiles as cleanly as any DLL on your disk. Understanding how to read them is also the fastest way to understand what you must not put in them.

What ships to the browser

When a Blazor WebAssembly app loads, it fetches a manifest — _framework/blazor.boot.json — that lists every assembly the app needs, each with a filename and an integrity hash. The browser then downloads those files from _framework/ . In current .NET they arrive as webcil : your PE assembly wrapped in a WebAssembly-compatible container.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.