Skip to content

Publish standalone WASM w/o an HTML doc #36554

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
guardrex merged 3 commits into from
Jan 12, 2026
Merged

Publish standalone WASM w/o an HTML doc #36554

Changes from 1 commit
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ab5eede
Publish standalone WASM w/o an HTML doc
guardrex Dec 29, 2025
f383b59
Updates
guardrex Jan 12, 2026
ef5240c
Update aspnetcore/blazor/host-and-deploy/webassembly/index.md
guardrex Jan 12, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions aspnetcore/blazor/host-and-deploy/webassembly/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -327,6 +327,14 @@ A *standalone deployment* serves the Blazor WebAssembly app as a set of static f

Standalone deployment assets are published into either the `/bin/Release/{TARGET FRAMEWORK}/publish/wwwroot` or `bin/Release/{TARGET FRAMEWORK}/browser-wasm/publish` folder, where the `{TARGET FRAMEWORK}` placeholder is the target framework.

:::moniker range=">= aspnetcore-10.0"

## Publish without an HTML document

When an app isn't using an HTML document produced as part of the .NET build/publish process, there's no place to write the site's [import map](https://developer.mozilla.org/docs/Web/HTML/Element/script/type/importmap). For example, this scenario occurs when publishing a standalone Blazor app for consumption by a JavaScript/SPA app through a [Blazor custom element](xref:blazor/components/js-spa-frameworks#blazor-custom-elements). To avoid problems loading app resources on the client, you must disable [fingerprinting](xref:blazor/fundamentals/static-files#fingerprint-client-side-static-assets-in-standalone-blazor-webassembly-apps) or build a [custom boot resources loader](xref:blazor/fundamentals/startup#load-client-side-boot-resources).
Comment thread
guardrex marked this conversation as resolved.
Outdated

:::moniker-end

## Azure App Service

Blazor WebAssembly apps can be deployed to Azure App Services on Windows, which hosts the app on IIS.
Expand Down