Skip to content

Conversation

guardrex
Copy link
Collaborator

@guardrex guardrex commented May 7, 2025

Fixes #35273

The Migration article will explain adding the markup to standalone WASM apps, and that guidance is typically created much later in the release cycle (RC time frame).


Internal previews

📄 File 🔗 Preview link
aspnetcore/blazor/fundamentals/static-files.md aspnetcore/blazor/fundamentals/static-files

@guardrex
Copy link
Collaborator Author

guardrex commented May 9, 2025

@maraf ... No rush on this ... just a reminder ping that this is here.

UPDATE (5/12): I'll merge by mid-day today (Monday) to unblock me for the final round of P4 updates.

@guardrex
Copy link
Collaborator Author

guardrex commented May 12, 2025

This is blocking now, so I'll need to go ahead and merge it.

The blocking problems with multiple PRs working on What's New content should go away at P5 or later 🤞 because we'll be adopting the new coverage approach where PU engineers will supply all preview content to me by two weeks before preview release and all content will go on one PR.

If you spot problems with this, ping me here, and I'll get a patch PR in place.

I'll get the two steps for this in place in the Migration article in the RC time frame when that article is fleshed out. Readers of this content will follow the "for more information" link to see the two aspects in the reference guidance.

@guardrex guardrex merged commit 7c93ffd into main May 12, 2025
3 checks passed
@guardrex guardrex deleted the guardrex/blazor-preload-wasm branch May 12, 2025 13:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Pre4] Preload Blazor WebAssembly resources to improve startup time

1 participant