Fix Blazor Wasm.Performance benchmarks build #64148
Merged
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
It currently runs into a known issue with fingerprinting that is fixed in 10.0 RTM. Disabling fingerprinting for now as a workaround.
maraf
approved these changes
Oct 24, 2025
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a build issue in the Blazor WebAssembly Performance benchmarks by disabling JavaScript fingerprinting as a workaround for a known issue that will be resolved in .NET 10.0 RTM.
Key Changes:
- Added MSBuild property to disable Blazor JavaScript fingerprinting during the publish step
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
It currently runs into a known issue with fingerprinting that is fixed in 10.0 RTM. Disabling fingerprinting for now as a workaround.