Go to file
Jass Bagga 1d00bb449f
Merge pull request #387 from aspnet/release/2.1
Move layout and partial script to Shared dir (#368)
2018-03-20 15:18:13 -07:00
.vscode
build Merge branch 'release/2.1' into jbagga/merge/release/2.1 2018-03-19 16:31:39 -07:00
migrations Add update migrations script (#376) 2018-03-20 09:45:53 -07:00
src Move layout and partial script to Shared dir (#368) 2018-03-20 15:17:50 -07:00
test Merge branch 'release/2.1' into dev 2018-03-20 13:47:26 -07:00
.appveyor.yml
.gitignore
.travis.yml
CONTRIBUTING.md
Directory.Build.props
Directory.Build.targets
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md
Templating.sln Removing Microsoft.AspNetCore.SpaTemplates project and friends 2018-03-20 13:46:11 -07:00
build.cmd
build.sh
korebuild-lock.txt Branching for 2.1.0-preview2 2018-03-16 11:17:31 -07:00
korebuild.json Update KoreBuild channel 2018-03-16 12:34:38 -07:00
run.cmd
run.ps1
run.sh
version.props Update version prefix to preview3 2018-03-16 11:28:40 -07:00

README.md

Templates

AppVeyor: AppVeyor

Getting Started

ASP.NET Templates provide project templates which are used in .NET Core for creating ASP.NET Core applications.

This project is part of ASP.NET Core. You can find samples, documentation and getting started instructions for ASP.NET Core at the Home repo.

Building Templates

  • Running build.cmd in this repo requires NPM which can be installed from https://nodejs.org/en/.
  • The ASP.NET localhost development certificate must also be installed and trusted or else you'll get a test error "Certificate error: Navigation blocked".
  • build.cmd (or build /t:package to avoid tests) will produce NuGet packages for each class of template in the artifacts directory. These can be installed via dotnet new -i {nugetpackage path}
  • You also need to get the packages these templates depend on into your package cache or else dotnet new restore will fail. The easiest way to get them to run is by letting the build run at least 1 test.