Blazorpack -

You ship a Blazor WebView inside a .NET MAUI or WPF shell. The user installs your app. Behind the scenes, your Blazor UI is still being served from embedded files. It works… but doesn’t it feel like your desktop app is pretending to be a website?

They wanted . No dependencies. Just click and run. blazorpack

The : No runtime installation. Your user gets an EXE that contains Blazor’s WebAssembly runtime, your app, and a minimal embedded web host. It’s like Electron, but with C# and 1/10th the memory usage. But… Is It Production Ready? Honest answer: Not for everyone. You ship a Blazor WebView inside a

And sometimes, magic is exactly what shipping needs. Have you used BlazorPack or something similar? Let me know in the comments — I’d love to hear your “single EXE” war stories. It works… but doesn’t it feel like your

If you’ve built a Blazor Hybrid app (Blazor Hybrid), you know the magic: write C# and Razor once, run on web, desktop, and mobile. But there’s always that moment in deployment where things get awkward.

dotnet add package BlazorPack dotnet build -c Release blazorpack --input bin/Release/net8.0/wwwroot --output MyApp.exe That’s it. Your MyApp.exe is ready to ship. Interesting question. .NET already has dotnet publish --single-file for console apps, but not for Blazor WebAssembly. Microsoft’s official answer for desktop Blazor is Blazor Hybrid (MAUI/WPF), which does not produce a single EXE.