Description
As a result of discussion in AspNetCore #64282 I believe that the steps of publishing a standalone wasm app need to have the clarification that you have to disable fingerprinting or build a custom loader as blazor.webassembly.{fingerprint}.js won't directly load dotnet.{fingerprint}.js.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly/github-pages?view=aspnetcore-10.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/host-and-deploy/webassembly/github-pages.md
Document ID
d6757daf-a25a-d46e-332c-cf811379f44c
Platform Id
5b882726-278a-3456-9f74-77a3f563a191
Article author
@guardrex
Metadata
- ID: d6757daf-a25a-d46e-332c-cf811379f44c
- PlatformId: 5b882726-278a-3456-9f74-77a3f563a191
- Service: aspnet-core
- Sub-service: blazor
Related Issues
Description
As a result of discussion in AspNetCore #64282 I believe that the steps of publishing a standalone wasm app need to have the clarification that you have to disable fingerprinting or build a custom loader as blazor.webassembly.{fingerprint}.js won't directly load dotnet.{fingerprint}.js.
Page URL
https://learn.microsoft.com/en-us/aspnet/core/blazor/host-and-deploy/webassembly/github-pages?view=aspnetcore-10.0
Content source URL
https://github.com/dotnet/AspNetCore.Docs/blob/main/aspnetcore/blazor/host-and-deploy/webassembly/github-pages.md
Document ID
d6757daf-a25a-d46e-332c-cf811379f44c
Platform Id
5b882726-278a-3456-9f74-77a3f563a191
Article author
@guardrex
Metadata
Related Issues