LiveReloadServer -WebRoot c:/temp/mysite/web -port 5500 -UseSsl true NET Tool like this (requires that the Dotnet Core 3.0 SDK is installed): dotnet tool install -g LiveReloadServer If you want to take a look at this generic static file Web server with included LiveReload functionality, you can install the LiveReloadServer. As a bonus it also works with Razor Pages (with limitations) - all in a folder that you specify (or launch in). Make changes to resources in that folder and see the page in the browser updated. Point it at a foler of HTML resources and go. So my use case is to have a local Web static file Web Server that automatically has Live Reload enabled. I've talked a lot about Live Reload recently because I ended up integrating this functionality into a number of applications and frameworks to make it that much easier to build and debug applications. NET tool or as a self-contained EXE, so it's easy to share - even if it's just for myself on other machines. It's easy to build and just as easy to then publish that customized generic server as a. By writing my own I can customize and provide exactly the features I need. Yeah, I know there are lots of NodeJs tools that do this, but it's just as easy to create a standalone server in. One scenario I've been thinking about recently is to build a generic Web server that makes it easy to serve Web content from an arbitrary local folder - generically. I also have a host of local static documentation sites that I need to often tweak the HTML with and having a local Web Server that includes LiveReload functionality is very useful for quickly making small quick-fix changes. I have a lot of scenarios in desktop applications that need access to local Web content for rendering or preview functionality and having a quick way to display content is useful. I love the fact that you can easily create a self-contained, local web server with ASP.NET Core. ASP.NET Core makes it easy to create a Web application regardless of whether you want to create code in raw middleware, using traditional MVC Controllers and Views, or by using Razor Pages as well as static content.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |