You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The title says it all. The hot reload is applied, and the component is generated and loaded again, but you can't see those changes until you instance that component again from Blazor.
.NET 6 RC1
Execution of the StateHasChanged method after the hot-reload tasks may solve that issue, just as we can do with Wasm or Server.
The text was updated successfully, but these errors were encountered:
The title says it all. The hot reload is applied, and the component is generated and loaded again, but you can't see those changes until you instance that component again from Blazor.
.NET 6 RC1
Execution of the StateHasChanged method after the hot-reload tasks may solve that issue, just as we can do with Wasm or Server.
The text was updated successfully, but these errors were encountered: