---
title: "Discussion on \"Decompiling a Blazor WebAssembly App: Reading the .NET DLLs the Browser Downloaded\" | Hashnode"
description: "Discussion on \"Decompiling a Blazor WebAssembly App: Reading the .NET DLLs the Browser Downloaded\". 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 c"
url: "https://hashnode.com/posts/decompiling-a-blazor-webassembly-app-reading-the-net-dlls-the-browser-downloaded/6af405e79868be71ba1a7e32"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Decompiling a Blazor WebAssembly App: Reading the .NET DLLs the Browser Downloaded](https://delta1labs.hashnode.dev/decompiling-a-blazor-webassembly-app-reading-the-net-dlls-the-browser-downloaded?utm_source=hashnode&utm_medium=feed)

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 c

15h ago · 4 min read · delta1labs.hashnode.dev  
Read the article

-   [#decompilation](https://hashnode.com/tag/decompilation)
-   [#dotnet](https://hashnode.com/tag/dotnet)
-   [#blazor](https://hashnode.com/tag/blazor)

## Written by

[Zero Heartbeat](https://hashnode.com/@clustron)

@clustron

  
[View profile](https://hashnode.com/@clustron)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.