Go to file
Ryan Brandenburg 2ca560f0b2 Don't tell people to run selenium themselves 2018-11-14 09:52:48 -08:00
.vscode
.vsts-pipelines Update to new templates 2018-10-31 09:43:13 -07:00
build React to Razor.Design package removal 2018-11-07 13:16:16 -08:00
migrations
scripts Merge pull request #805 from dotnet-maestro-bot/merge/release/2.2-to-master 2018-10-25 16:23:28 -07:00
src React to Razor.Design package removal 2018-11-07 13:16:16 -08:00
test Merge pull request #805 from dotnet-maestro-bot/merge/release/2.2-to-master 2018-10-25 16:23:28 -07:00
.appveyor.yml
.gitattributes
.gitignore
CONTRIBUTING.md
Directory.Build.props
Directory.Build.targets
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md Don't tell people to run selenium themselves 2018-11-14 09:52:48 -08:00
Templating.sln
build.cmd
build.sh
korebuild-lock.txt Update code signing config to exclude .js and .ttf files in template packages 2018-10-26 11:51:23 -07:00
korebuild.json
run.cmd
run.ps1
run.sh
version.props Merge branch 'release/2.2' 2018-10-26 13:39:01 -07:00

README.md

Templates

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.