Skip to content

Conversation

@guardrex
Copy link
Collaborator

@guardrex guardrex commented Dec 18, 2024

Fixes #34392

Thanks @nicholasyin! 🚀 ... This improves the guidance with WASM and the environment variable for local development runs. I also include some new guidance for Nginx and Apache file server hosting scenarios. I'm waiting for the product unit to get back to me; but if I don't hear from them by EOD, I'll probably go ahead and merge this. I'll patch it later based on my discussion with them. Thanks for writing in on this, and keep your 👁️ on dotnet/aspnetcore#59456 for some possible improved control in a future release of Blazor.

UPDATE: I just heard back that they're too busy to look right now. I'll make a final pass on Thursday morning. Since this matches the behavior of the framework, I'll go ahead and merge it tomorrow morning. I'll patch it later if anything comes up.


Internal previews

📄 File 🔗 Preview link
aspnetcore/blazor/fundamentals/environments.md aspnetcore/blazor/fundamentals/environments

@guardrex guardrex merged commit 5c792fc into main Dec 19, 2024
3 checks passed
@guardrex guardrex deleted the guardrex/blazor-wasm-environment branch December 19, 2024 10:44
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.

No example usage for setting blazor-environment header in a standalone Blazor wasm app not using IIS

2 participants