Skip to content

Conversation

MackinnonBuck
Copy link
Member

Since the dev server no longer calls UseBlazorFrameworkFiles(), we need to manually add the Blazor-Environment header when applicable.

Fixes #57941

@MackinnonBuck MackinnonBuck added the area-blazor Includes: Blazor, Razor Components label Sep 19, 2024
@MackinnonBuck MackinnonBuck requested a review from a team as a code owner September 19, 2024 19:08
@MackinnonBuck
Copy link
Member Author

/backport to release/9.0-rc2

Copy link
Contributor

Started backporting to release/9.0-rc2: https://github.com/dotnet/aspnetcore/actions/runs/10949630835

Co-authored-by: Stephen Halter <halter73@gmail.com>
@MackinnonBuck MackinnonBuck merged commit e9160be into main Sep 20, 2024
27 checks passed
@MackinnonBuck MackinnonBuck deleted the mbuck/fix-devserver-environment branch September 20, 2024 18:07
@dotnet-policy-service dotnet-policy-service bot added this to the 10.0-preview1 milestone Sep 20, 2024
captainsafia pushed a commit that referenced this pull request Dec 31, 2024
…ent` header (#57971)

Co-authored-by: Stephen Halter <halter73@gmail.com>
captainsafia pushed a commit that referenced this pull request Feb 11, 2025
…ent` header (#57971)

Co-authored-by: Stephen Halter <halter73@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-blazor Includes: Blazor, Razor Components
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Blazor WebAssembly Standalone App targeting .net 9 runs in production mode when started from VS in debug mode
4 participants