Go to file
Jass Bagga 1fe30aabbe
Skip WebApiTemplate_Works_NetCore test temporarily (#401)
2018-03-24 17:45:24 -07:00
.vscode
build Fix package metadata to match default settings for aspnetcore (#389) 2018-03-21 18:10:31 -07:00
src Remove EF.Tools reference 2018-03-23 12:09:46 -07:00
test Skip WebApiTemplate_Works_NetCore test temporarily (#401) 2018-03-24 17:45:24 -07:00
.appveyor.yml
.gitignore
.travis.yml
CONTRIBUTING.md
Directory.Build.props Fix package metadata to match default settings for aspnetcore (#389) 2018-03-21 18:10:31 -07:00
Directory.Build.targets
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md
Templating.sln
build.cmd
build.sh
korebuild-lock.txt Fix package metadata to match default settings for aspnetcore (#389) 2018-03-21 18:10:31 -07:00
korebuild.json
run.cmd
run.ps1
run.sh
version.props

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.