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
I've a suggestion for hot-reload with Blazor to give a less interrupted experience and keep you more in the flow, giving a reload experience similar to angular:
At the moment if you change something and it cannot hot-reload it in, you get a pop-up and need to stop and restart debugging which closes the browser.
Would it be possible in this situation instead to put up a similar prompt to let the user know, but on reload:
Keep the browser window open
Suspend the app with an overlay or holding page (like when the signalR connection drops)
Do the full compile
Once compiled/restarted, reload the browser window retaining the original path.
That gives a less interrupted experience. You'll lose the state of your page (unless you've coded something to retain it in storage), but will at least be back on the page you where working on with the app re-loaded.
Bonus:
In a .NET Aspire context it could work the same as above, but keep the Aspire host running as well, and recompile/restart the container apps in the host.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've a suggestion for hot-reload with Blazor to give a less interrupted experience and keep you more in the flow, giving a reload experience similar to angular:
At the moment if you change something and it cannot hot-reload it in, you get a pop-up and need to stop and restart debugging which closes the browser.
Would it be possible in this situation instead to put up a similar prompt to let the user know, but on reload:
That gives a less interrupted experience. You'll lose the state of your page (unless you've coded something to retain it in storage), but will at least be back on the page you where working on with the app re-loaded.
Bonus:
In a .NET Aspire context it could work the same as above, but keep the Aspire host running as well, and recompile/restart the container apps in the host.
Beta Was this translation helpful? Give feedback.
All reactions