From ab5eede206daa46c2f561e4f87badcc3352cd88c Mon Sep 17 00:00:00 2001 From: guardrex <1622880+guardrex@users.noreply.github.com> Date: Mon, 29 Dec 2025 08:12:29 -0500 Subject: [PATCH 1/3] Publish standalone WASM w/o an HTML doc --- aspnetcore/blazor/host-and-deploy/webassembly/index.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/aspnetcore/blazor/host-and-deploy/webassembly/index.md b/aspnetcore/blazor/host-and-deploy/webassembly/index.md index 9cc6b6e09084..caafb6cdbf81 100644 --- a/aspnetcore/blazor/host-and-deploy/webassembly/index.md +++ b/aspnetcore/blazor/host-and-deploy/webassembly/index.md @@ -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). + +:::moniker-end + ## Azure App Service Blazor WebAssembly apps can be deployed to Azure App Services on Windows, which hosts the app on IIS. From f383b59d54ae35e45d99148f2d8d6e89cbda0b1f Mon Sep 17 00:00:00 2001 From: guardrex <1622880+guardrex@users.noreply.github.com> Date: Mon, 12 Jan 2026 07:40:49 -0500 Subject: [PATCH 2/3] Updates --- aspnetcore/blazor/host-and-deploy/webassembly/index.md | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/aspnetcore/blazor/host-and-deploy/webassembly/index.md b/aspnetcore/blazor/host-and-deploy/webassembly/index.md index caafb6cdbf81..c084ca1641be 100644 --- a/aspnetcore/blazor/host-and-deploy/webassembly/index.md +++ b/aspnetcore/blazor/host-and-deploy/webassembly/index.md @@ -331,7 +331,12 @@ Standalone deployment assets are published into either the `/bin/Release/{TARGET ## 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). +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, disable [fingerprinting](xref:blazor/fundamentals/static-files#fingerprint-client-side-static-assets-in-standalone-blazor-webassembly-apps) for `blazor.webassembly.js` and `dotnet.js` using *either* of the following approaches: + +* Remove the fingerprint marker (`#[.{fingerprint}]`) from the `blazor.webassembly.js` Blazor script `src` attribute in `wwwroot/index.html`. After publishing the app, remove the fingerprint marker from `dotnet.js` by renaming the `dotnet.{FINGERPRINT}.js` file to `dotnet.js`, where the `{FINGERPRINT}` placeholder is the file's fingerprint. Remove the `` MSBuild property (or set it to `false`) in the app's project file (`.csproj`). +* Build a [custom boot resources loader](xref:blazor/fundamentals/startup#load-client-side-boot-resources) that strips off the fingerprint marker from the `blazor.webassembly.js` and `dotnet.js` files. :::moniker-end From ef5240c1a405400611b462fe0ff4c04793918bb6 Mon Sep 17 00:00:00 2001 From: Luke Latham <1622880+guardrex@users.noreply.github.com> Date: Mon, 12 Jan 2026 08:28:47 -0500 Subject: [PATCH 3/3] Update aspnetcore/blazor/host-and-deploy/webassembly/index.md MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Marek FiĊĦera --- aspnetcore/blazor/host-and-deploy/webassembly/index.md | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/aspnetcore/blazor/host-and-deploy/webassembly/index.md b/aspnetcore/blazor/host-and-deploy/webassembly/index.md index c084ca1641be..09eb699c9b34 100644 --- a/aspnetcore/blazor/host-and-deploy/webassembly/index.md +++ b/aspnetcore/blazor/host-and-deploy/webassembly/index.md @@ -333,10 +333,7 @@ Standalone deployment assets are published into either the `/bin/Release/{TARGET 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, disable [fingerprinting](xref:blazor/fundamentals/static-files#fingerprint-client-side-static-assets-in-standalone-blazor-webassembly-apps) for `blazor.webassembly.js` and `dotnet.js` using *either* of the following approaches: - -* Remove the fingerprint marker (`#[.{fingerprint}]`) from the `blazor.webassembly.js` Blazor script `src` attribute in `wwwroot/index.html`. After publishing the app, remove the fingerprint marker from `dotnet.js` by renaming the `dotnet.{FINGERPRINT}.js` file to `dotnet.js`, where the `{FINGERPRINT}` placeholder is the file's fingerprint. Remove the `` MSBuild property (or set it to `false`) in the app's project file (`.csproj`). -* Build a [custom boot resources loader](xref:blazor/fundamentals/startup#load-client-side-boot-resources) that strips off the fingerprint marker from the `blazor.webassembly.js` and `dotnet.js` files. +To avoid problems loading app resources on the client, disable [fingerprinting](xref:blazor/fundamentals/static-files#fingerprint-client-side-static-assets-in-standalone-blazor-webassembly-apps) for `blazor.webassembly.js` and `dotnet.js` by removing `` MSBuild property (or set it to `false`) in the app's project file (`.csproj`). :::moniker-end