7bde7399e9
This package does not need to be in the project until someone uses Visual Studio code generation. Visual Studio will automatically add this package when scaffolding is used for the first time, so it's unnecessary to put this in our templates. |
||
|---|---|---|
| .vscode | ||
| .vsts-pipelines | ||
| build | ||
| migrations | ||
| scripts | ||
| src | ||
| test | ||
| .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 | ||
| korebuild.json | ||
| run.cmd | ||
| run.ps1 | ||
| run.sh | ||
| version.props | ||
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(orbuild /t:packageto avoid tests) will produce NuGet packages for each class of template in the artifacts directory. These can be installed viadotnet new -i {nugetpackage path}- You also need to get the packages these templates depend on into your package cache or else
dotnet newrestore 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 startRunbuild.cmd /t:Test