* Enable single pages directory * Rename Index.cshtml to Host.cshtml * Get rid of _ViewImports.cshtml |
||
|---|---|---|
| .. | ||
| Web.Client.ItemTemplates | ||
| Web.ItemTemplates | ||
| Web.ProjectTemplates | ||
| Web.Spa.ProjectTemplates | ||
| migrations | ||
| scripts | ||
| test | ||
| testassets/DotNetToolsInstaller | ||
| .gitignore | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| GenerateContent.targets | ||
| ProjectTemplates.sln | ||
| README.md | ||
| SetPackageProperties.targets | ||
| THIRD-PARTY-NOTICES | ||
| TemplateProjects.props | ||
| build.cmd | ||
| templates.nuspec | ||
README.md
Templates
Getting Started
These are project templates which are used in .NET Core for creating ASP.NET Core applications.
Building Templates
-
Run
. .\activate.ps1if you haven't already. -
Run
build.cmd -all -packin the repository root to build all of the dependencies. -
Run
build.cmdin this directory will produce NuGet packages for each class of template in the artifacts directory. -
Because the templates build against the version of
Microsoft.AspNetCore.Appthat was built during step 2 it is NOT advised that you install templates created on your local machine viadotnet new -i [nupkgPath]. Instead, use theRun-[Template]-Locally.ps1scripts in the script folder. These scripts dodotnet new -iwith your packages, but also apply a series of fixes and tweeks to the created template which keep the fact that you don't have a productionMicrosoft.AspNetCore.Appfrom interfering. -
The ASP.NET localhost development certificate must also be installed and trusted or else you'll get a test error "Certificate error: Navigation blocked".
** Note** Templating tests require Visual Studio unless a full build (CI) is performed.