https://github.com/spongessuck/angular-universal-dotnet-starter
Angular 2 app seed using the Universal CLI and .NET Core for server-side rendering.
https://github.com/spongessuck/angular-universal-dotnet-starter
angular dotnet-core server-side-rendering
Last synced: 3 months ago
JSON representation
Angular 2 app seed using the Universal CLI and .NET Core for server-side rendering.
- Host: GitHub
- URL: https://github.com/spongessuck/angular-universal-dotnet-starter
- Owner: spongessuck
- Created: 2017-02-09T03:18:49.000Z (over 8 years ago)
- Default Branch: master
- Last Pushed: 2017-02-09T20:10:41.000Z (over 8 years ago)
- Last Synced: 2025-01-16T09:58:33.310Z (4 months ago)
- Topics: angular, dotnet-core, server-side-rendering
- Language: TypeScript
- Size: 16.6 KB
- Stars: 1
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Angular-Universal-Dotnet-Starter
This project was generated with [universal-cli](https://github.com/devCrossNet/universal-cli) version 1.0.0-alpha.universal.3.
This implementation replaces the default Express-based server-side rendering solution with one using the .NET Core runtime. While the pre-rendering application can be run on its own, it has been configured to be hosted via a reverse-proxy between IIS and its Kestrel server. Refer to [this page](https://docs.microsoft.com/en-us/aspnet/core/publishing/iis) for more information about publishing .NET Core apps to IIS.
## Setup
0. Install the [.NET Core SDK](https://www.microsoft.com/net/core).
0. Install the [Angular Universal CLI](https://github.com/devCrossNet/universal-cli).
0. Clone this repo.
0. `cd` into the project directory.
0. Run `npm install`.
0. Run `dotnet restore`.
## Development server
Run `ung serve` for a dev server. Navigate to `http://localhost:4200/`. The app will automatically reload if you change any of the source files.
## Code scaffolding
Run `ung generate component component-name` to generate a new component. You can also use `ung generate directive/pipe/service/class`.
## Build
Run `ung build` to build the project. The build artifacts will be stored in the `dist/` directory. Use the `-prod` flag for a production build.
## Running unit tests
Run `ung test` to execute the unit tests via [Karma](https://karma-runner.github.io).
## Running end-to-end tests
Run `ung e2e` to execute the end-to-end tests via [Protractor](http://www.protractortest.org/).
Before running the tests make sure you are serving the app via `ung serve`.
## Deploying to IIS
0. [Configure IIS to run .NET Core apps](https://docs.microsoft.com/en-us/aspnet/core/publishing/iis).
0. Using IIS, set up a new website, or add a directory to an existing website, and configure it as an application using the application pool set up in step 0.
0. Run `npm run build` to build the Angular app and publish the prerendering application. If you're app will sit in a subfolder on your site, use the `--bh` flag to set the base URL tag in your `index.html` file (i.e. `--bh /subfolder/`)
0. Copy the contents of `dist` to your IIS server.
0. Run `npm install --production` in the application folder.
## Further help
To get more help on the `universal-cli` use `ung --help` or go check out the [Universal-CLI README](https://github.com/devCrossNet/universal-cli/blob/master/README.md).