Consider adding antivirus/firewall bypasses to the site

[peterthorpe81]

Blazor WASM sites often get blocked by corporate firewalls because of the fetch of dll's. Firewalls will often identify them as unsafe due to the dll extension or the file starting with the "MZ" header (executable) meaning you can't access the tryblazor or mudblazor.com sites behind a lot of corporate firewalls.

This nuget package works well to bypass the issue by Xor'ing the dll's and changing the file extension on publish. https://github.com/stavroskasidis/BlazorWasmAntivirusProtection

[henon]

Interesting. Not sure how much work this is gonna be. Try.MudBlazor compiles assemblies on the fly and injects them into the browser cache before reloading the iframe and restarting Blazor with the newly compiled resources.

[ScarletKuro]

I would wait when Webcil will be fully released and supported in .NET.