You also need to run 2 terminal windows for this particular solution to work. Browser-Sync - a client side live reload server/proxy.
#WEBPACK LIVERELOAD BROWSER CODE#
There are however other, better solutions and in this post I'll talk about using a couple of tools in combination to provide pretty good Live Reload functionality for: It also only works in Visual Studio so if you're not on Windows or use another tool like Rider or VS Code it's not useful. That's too bad because it looked really promising. It's still there, neglected and there are options on the debug toolbar, but other than for CSS Browser Link it never really worked reliably for me. Microsoft sort of added some tooling into Visual Studio called Browser Link a long time ago with Visual Studio tooling, but this originally promising project died a quiet death and never really took off. That's all nice and neat for client side code where live reload is common, but on the server side there isn't really an easy comprehensive solution that provides similar functionality. If you've never used live reload functionality before it's quite a game changer for productivity, while working on iterative code - especially HTML and CSS Layout tweaks that often go through the "make a tiny change, see what it looks like and then tweak it some more" phase.
If you're using any client side framework like Angular, Vue or React they all come with integrated CLIs that provide instant live reloading of content as soon as you make a change. For ASP.NET Core applications this is a cleaner way that doesn't require an additional command line tool.Ĭlient side in-browser hot reloading is one of the most compelling features of client side development. There's a newer post that uses an ASP.NET Core middleware component that can integrate Live Reload right into your ASP.NET Core application. This post uses a a third party tool called BrowserSync to handle client side refreshing.
0 kommentar(er)
