[release/10.0] [Blazor][HotReload] Capture the execution context before calling RenderRootComponentsOnHotReload #63847
+90
−3
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
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=80&v=4){kind=small}
maraf
approved these changes
Sep 29, 2025
lewing
added
the
feature-hot-reload
|
With video verification |
|
@javiercn has this one gone thru ask-mode yet? |
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.
Backport of #63846 to release/10.0
/cc @javiercn
[Blazor][HotReload] Capture the execution context before calling RenderRootComponentsOnHotReload
Ensure ExecutionContext flows to hot reload re-renders
Description
ExecutionContextwhen subscribing toHotReloadManager.OnDeltaAppliedRenderRootComponentsOnHotReloadvia a helper that restores the captured context, preserving AsyncLocal valuesFixes #45741
Customer Impact
AsyncLocal-backed data (e.g., culture, logging scopes, circuit state) was being lost after hot reload, leading to incorrect behavior on subsequent renders.
Regression?
Risk
Changes are scoped to the hot reload subscription path, reuse existing render logic, and are exercised by automated tests.
Verification
Packaging changes reviewed?