Repository navigation
Hot Reload for Blazor #5456
Description
- Mono Method Body Replacement
- Build performance optimization
- Via
dotnet watch - Development middleware (websocket connection to receive updates)
Metadata
Metadata
Assignees
Labels
This issue tracks a big effort which can span multiple issuesThis issue has been fixedGroups multiple user stories. Can be grouped under a theme.This issue requires design work before implementating.Work that we can't release withoutThis issue impacts most of the customersIncludes: Blazor, Razor ComponentsThis issue represents an ask for new feature or an enhancement to an existing oneThis issue is related to the Hot Reload feaatureThis label is used by an internal tool
Activity
SteveSandersonMS commentedon Mar 16, 2018
See dotnet/blazor#193 for status updates on this work item.
martasp commentedon Mar 23, 2018
For now, we can use
dotnet watch runand recompile every time when the change occurs.Just using this in csproj file :
<DotNetCliToolReference Include="Microsoft.DotNet.Watcher.Tools" Version="2.0.0" /><Watch Include="**\*.cshtml"/>danroth27 commentedon Apr 4, 2018
We've hit a snag with live reload for 0.2.0, so moving this out until we can work through a more robust design.
mkArtakMSFT commentedon Mar 20, 2019
@danroth27, what's #4056 then? Should it be closed?
165 remaining items
BrunoBlanes commentedon Nov 23, 2020
@hannespreishuber that is a terrible way to provide feedback if that was your intent. Try opening an issue and following the template.
Filipowicz251 commentedon Nov 23, 2020
Just small feedback regarding this statement. For me and using "Auto build and refresh option" (what @porkopek suggested) is taking more like 5 secs. Yes, it is not 1 sec as with Livesharp but it is quite fast and it is working :)
I did try Livesharp, but for me it was breaking the external JS on the site (I did have some slider revolution part and after livesharp was sending an update, the js on the site was broken)
mrlife commentedon Nov 23, 2020
@pranavkm @jongalloway Possible to update the VS Mac roadmap?
szalapski commentedon Nov 23, 2020
Hmmm, auto-refreshing the browser in .NET 5 using
dotnet watch rundoesn't seem to be working for me. I used to use Westwind.AspNetCore.LiveReload, but I have removed it to try this out. When I make a change, the app rebuilds and restarts web server for me, but the browser doesn't refresh. This is a project I upgraded from .NET Core 3.1. Is there anything that needs to be done in startup.cs to enable this? What else could be interfering? How can I troubleshoot?BrunoBlanes commentedon Nov 23, 2020
@szalapski Have you noticed if the browser isn't refreshing before the server finishes starting up? I've seen that happen a few times. I don't know if it is by design.
danroth27 commentedon Dec 1, 2020
@szalapski Does auto refresh work if you start from a new project? Have you set
"launchBrowser": truein launchSettings.json?gojanpaolo commentedon Dec 1, 2020
dotnet watch runalso just stops working for me sometimes. Closing all VS instances and then rerunningdotnet watch runseems to solve the issue. I'll see if I can drill down the root cause.danroth27 commentedon Dec 1, 2020
For folks hitting issues with
dotnet watch runplease open new GitHub issues with any details you have about how to reproduce the problem, so that we don't conflate those investigations with the hot reload work we're working on for .NET 6.mkArtakMSFT commentedon Sep 16, 2021
Closing this issue as we're done with the work we planned to deliver for 6.0.
There are still many improvements to do in this area which are going to be tracked as part of dotnet/runtime#57365