Enable WasmFingerprintAssets for cache busting #166
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.
The
HttpClientmethod has been removed, and DLL data is now retrieved directly from thedotnet-resources-/.This allows cache busting to be applied via
WasmFingerprintAssets.Previously, when running from
TryMudBlazor.Server, accessing links likehttps://localhost:5001/_framework/Microsoft.AspNetCore.Components.WebAssembly.dllwould result in a 404 error. The correct link should have beenhttps://localhost:5001/_framework/Microsoft.AspNetCore.Components.Forms.vnx3zz3bws.dll, but we couldn't retrieve the fingerprint (e.g.,vnx3zz3bws) for the DLLs. It seems the legacy method of hosting WASM+ASP.NET Core together doesn't fully support this feature because theResourceAssetCollectiondidn't return the necessary fingerprint information.Therefore, using JS is the most optimal solution.
This approach works for both running as standalone WASM from
TryMudBlazor.Clientand the cohosted version fromTryMudBlazor.Server.When testing, please ensure to test both versions.