Skip to content
Permalink
Browse files

remove ng server option, .html requires beign served by SS

  • Loading branch information...
mythz committed Aug 23, 2019
1 parent 5bbf4d4 commit ee7ab35e042631ebb3a050959a6314b6dc969b63
Showing with 0 additions and 9 deletions.
  1. +0 −1 MyApp/package.json
  2. +0 −8 README.md
@@ -5,7 +5,6 @@
"postinstall": "npm run build",
"ng": "ng",
"dev": "ng build --aot --watch",
"start": "ng serve --proxy-config proxy.config.json",
"dtos": "tsd-ref && ts-ref",
"build": "ng build --prod",
"publish": "npm run build && dotnet publish -c Release",
@@ -20,14 +20,6 @@ This initially generates a full development build of your Web App then stays run

Each change updates the output dev resources so even if you stop the dev task your Web App remains in a working state that’s viewable when running the ASP.NET Web App.

### Live reload with built-in Dev Server

The alternative dev workflow is to run the `serve` npm or gulp script to run Create React App's built-in Webpack dev server:

$ npm run serve

This launches the Webpack dev server listening at `http://localhost:4200/` and configured to proxy all non-Webpack HTTP requests to the ASP.NET Web App where it handles all Server API requests. The benefit of viewing your App through the Webpack dev server is its built-in Live Reload feature where it will automatically reload the page as resources are updated.

### Watched .NET Core builds

.NET Core projects can also benefit from Live Coding using dotnet watch which performs a “watched build” where it automatically stops, recompiles and restarts your .NET Core App when it detects source file changes. You can start a watched build from the command-line with:

0 comments on commit ee7ab35

Please sign in to comment.
You can’t perform that action at this time.