Go to file
Nate McMaster 8e60b8b311
Update branding to 2.1.6-servicing (#765)
2018-10-09 09:30:45 -07:00
.vscode
build Add Microsoft.AspNetCore.Razor.Design to templates (#674) 2018-08-28 09:41:15 -07:00
migrations [Review] Updated migrations and scripts (#484) 2018-05-03 13:22:26 -07:00
src Add Microsoft.AspNetCore.Razor.Design to templates (#674) 2018-08-28 09:41:15 -07:00
test Revert "Add package version to Microsoft.AspNetCore.App in project templates" 2018-07-18 13:11:01 -07:00
.appveyor.yml Update dependencies.props to 2.1.0-preview-28193, build tools to 2.1.0-preview1-1010 [ci skip] 2018-01-31 15:01:13 -08:00
.gitignore Add package version to Microsoft.AspNetCore.App in project templates 2018-07-03 16:53:46 -07:00
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 Add package version to Microsoft.AspNetCore.App in project templates 2018-07-03 16:53:46 -07:00
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json Upgrade to build tools 2.1.0-preview1-15651 2017-12-28 16:07:17 -08:00
README.md Update README.md with build instructions (#211) 2018-01-29 09:37:31 -08:00
Templating.sln Use dotnet-ef package (#433) 2018-04-03 10:36:06 -07:00
build.cmd
build.sh
korebuild-lock.txt Add Microsoft.AspNetCore.Razor.Design to templates (#674) 2018-08-28 09:41:15 -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 branding to 2.1.6-servicing (#765) 2018-10-09 09:30:45 -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.