335c9be7b4
This simplifies the way that we publish files to our network drop share. Changes: * Instead of explicitly listing every file that needs to publish, use directories to classify packages and artifacts into different categories. * Add documentation for the expected layout of artifacts/ * Remove the need for static analysis to determine which packages go to which project * Add the MSBuild property "IsProductPackage" to .csproj files which ship as a package to NuGet.org. |
||
|---|---|---|
| .. | ||
| build | ||
| migrations | ||
| scripts | ||
| src | ||
| test | ||
| .gitignore | ||
| Directory.Build.props | ||
| Directory.Build.targets | ||
| NuGetPackageVerifier.json | ||
| README.md | ||
| Templating.sln | ||
| 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.