[Pre3] Blazor WASM fingerprinting and environment property #35057
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Mar 26, 2025
maraf
reviewed
Mar 27, 2025
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as resolved.
This comment was marked as resolved.
guardrex
changed the title
This comment was marked as resolved.
This comment was marked as resolved.
|
A rename is coming your way dotnet/sdk#47915 |
This comment was marked as resolved.
This comment was marked as resolved.
maraf
reviewed
Apr 2, 2025
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
|
This has the updates on it now. I split the BWA guidance from the standalone WASM guidance. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
danroth27
reviewed
Apr 5, 2025
danroth27
reviewed
Apr 6, 2025
|
|
||
| ### Set the environment in standalone Blazor WebAssembly apps | ||
|
|
||
| The `Properties/launchSettings.json` file is no longer used to control the environment in standalone Blazor WebAssembly apps. |
There was a problem hiding this comment.
@maraf This makes it sound like we made a breaking change here. Is the only impact on how you set the environment for standalone Blazor WebAssembly apps during development? Or is there also impact on existing ASP.NET Core hosted apps?
There was a problem hiding this comment.
Only standalone mode during development affected
danroth27
reviewed
Apr 6, 2025
Co-authored-by: Daniel Roth <[email protected]>
|
@danroth27 @maraf ... Are we good to go on this one?
That should wrap up Pre3 work, but I'll check one more time to see if I missed anything. |
mccoylstevens
pushed a commit
to POWER-OF-ATTORNEY/AspNetCore.Docs
that referenced
this pull request
May 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #35023
Addresses #34948
Addresses #34437
Fixes #35075
Covering two Blazor WASM features now on this PR ...
<WasmApplicationEnvironmentName>to set the environmentInternal previews