[Blazor] Add query string to dotnet.js import for cache busting in .NET 8.0 #63162
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.
This change adds a cache-busting query parameter to the
dotnet.js
import statement in the Blazor WebAssembly platform code to ensure browsers don't use cached versions from previous .NET releases when upgrading to .NET 8.0.Problem
When .NET 8.0 is released, browsers may continue to use cached versions of
dotnet.js
from previous .NET versions, potentially causing compatibility issues or preventing users from getting the latest runtime improvements.Solution
Modified the default source URL in
MonoPlatform.ts
to append?v=8.0
to thedotnet.js
URL:Impact
dotnet.js
files when .NET 8.0 is deployed instead of using cached versionsloadBootResource
is providedThe change specifically targets the scenario where the default dotnet.js loading mechanism is used, ensuring a smooth transition for users upgrading to .NET 8.0.
Fixes #63161.
💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.