Go to file
Pranav K b96c8ca3fe
Merge branch 'release/2.1' into dev
2018-03-16 12:34:42 -07:00
.vscode
build Update dependencies (#359) 2018-03-15 10:47:49 -07:00
src Split sqllite and sql server migrations (#348) 2018-03-13 11:41:16 -07:00
test Skip F# net framework test (#363) 2018-03-15 15:56:16 -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 Update project .gitignore. Closes #280 2018-02-02 22:27:44 +01:00
.travis.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
CONTRIBUTING.md
Directory.Build.props
Directory.Build.targets
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md Update README.md with build instructions (#211) 2018-01-29 09:37:31 -08:00
Templating.sln
build.cmd
build.sh
korebuild-lock.txt Update dependencies (#359) 2018-03-15 10:47:49 -07:00
korebuild.json 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
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.