Go to file
ASP.NET CI 28430a8c50 Update dependencies.props
[auto-updated: dependencies]
2018-04-29 12:34:40 -07:00
.vscode
build Update dependencies.props 2018-04-29 12:34:40 -07:00
migrations
src Merge branch 'release/2.1' into dev 2018-04-20 11:42:22 -07:00
test Respond to dotnet-ef target framework upgrade (#503) 2018-04-27 20:26:34 -07:00
.appveyor.yml
.gitignore
.travis.yml
CONTRIBUTING.md
Directory.Build.props
Directory.Build.targets Set NETStandardImplicitPackageVersion via dependencies.props 2018-04-19 16:45:24 -07:00
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md
Templating.sln
build.cmd
build.sh
korebuild-lock.txt Respond to dotnet-ef target framework upgrade (#503) 2018-04-27 20:26:34 -07:00
korebuild.json Branching for 2.1.0-rc1 2018-04-16 17:03:27 -07:00
run.cmd
run.ps1
run.sh
version.props Update version number to 2.2.0 2018-04-16 17:03:32 -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.