Fix issue with getting a 404 for blazor.server.js #1627
Merged
Conversation
This file contains 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
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.
Issue #, if available:
#1625
Description of changes:
With the creating the .NET 8 version of the test tool there was a breaking behavior in Blazor in how it static files were were handled to return turn the
_framework/blazor.server.js. In the process of diagnosing this error some debugging code was introduced for .NET 6 and the fix was added in a conditional block just for .NET 8. The debugging code was left in the .NET 6 condition cause the tool to break not return_framework/blazor.server.js. This PR restores the original behavior.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.