The Wayback Machine - https://web.archive.org/web/20210606020759/https://github.com/dotnet/aspnetcore/issues/33320
Skip to content

/ aspnetcore

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Blazor: Hot reload and WASM pre-render do not work together #33320

Open
jburman opened this issue Jun 6, 2021 · 0 comments
Open

Blazor: Hot reload and WASM pre-render do not work together #33320

jburman opened this issue Jun 6, 2021 · 0 comments

Comments

@jburman
Copy link

@jburman jburman commented Jun 6, 2021

App. is asp.net core hosted WASM app. with WebAssemblyPrerendered enabled.

Steps to repro. the issue...

  1. Updated from .net 5 to use .net 6 preview 4.
  2. At this point, running dotnet watch run works as expected (browser refreshes and shows updates as files change)
  3. Added hotReloadProfile aspnetcore to the Server app's run profile
  4. Running dotnet watch run indicates that hot reload is now enabled.
  5. Making a change triggers hot reload, however the update does not display in the web browser.
  6. Manually refreshing the page in the browser will briefly show the changed version and then it reverts back to the old version.
  7. Ctrl-R in the terminal will reload the app and show the changes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant
@jburman