This example project tries to retain most of the features of angular-cli while leveraging aspnet-core as an developement server and integrating the webpack build and features like hot-module-replacement into the aspnet-core application.
After checkout you should run dotnet restore and npm install. Visual Studio might do this automatically.
The aspnet core app will automatically build the client app with webpack on startup, which might take up to a few minutes.
Just choose the profile Self-host or IIS Express and run the application.
dotnet run
The aspnet-core features described here are implemented using the Microsoft.AspNetCore.SpaServices package.
Angular2 can use the push api for routing. This results in URLs that look like www.example.com/users/1 instead of www.example.com#/users/1 (mind the #). When reloading such an URL the server will always serve the index.html of your angular application.
The aspnet-core app will act as a full-features webpack dev-server. After running the app the console should read [hmr] connected. Try changing you angular components (html, ts, scss..) and hit save. The browser sould display the changes almost instantly.
The project was first generated with angular cli and then ejected. This project was generated with Angular CLI version 1.0.0.
Run ng generate component component-name to generate a new component. You can also use ng generate directive/pipe/service/class/module.
Run npm run build to build the project. The build artifacts will be stored in the wwwroot/ directory. Use the -prod flag for a production build.
Run npm run test to execute the unit tests via Karma.
Run npm run e2e to execute the end-to-end tests via Protractor.
Before running the tests make sure you are serving the app by starting your aspnet-core app. If you are using IIS as a host, make sure to edit the protractor.json to match your port number.
To get more help on the Angular CLI check out the Angular CLI README.