Go to file
Ryan Brandenburg a140f38810 Enhancments 2018-09-20 14:52:16 -07:00
.vscode
.vsts-pipelines
build Update dependencies.props 2018-09-16 12:31:05 -07:00
migrations
scripts Normalize FSharp templates and don't check in site.min.js 2018-09-13 14:41:32 -07:00
src Enhancments 2018-09-20 14:52:16 -07:00
test Normalize FSharp templates and don't check in site.min.js 2018-09-13 14:41:32 -07:00
.appveyor.yml
.gitattributes
.gitignore
CONTRIBUTING.md
Directory.Build.props
Directory.Build.targets
LICENSE.txt
NuGet.config
NuGetPackageVerifier.json
README.md
Templating.sln
build.cmd
build.sh
korebuild-lock.txt Update dependencies.props 2018-09-16 12:31:05 -07:00
korebuild.json
run.cmd
run.ps1
run.sh
version.props Update branding to 2.2.0-preview3 2018-09-05 16:36:37 -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.

Running end-to-end tests

Prerequisites:

  • Install selenium-standalone (requires Java 8 or 9)
  • Open JDK9
  • npm install -g selenium-standalone
  • selenium-standalone install
  • Chrome Run selenium-standalone start Run build.cmd /t:Test