History

Doug Bunting aee5e40803 Stabilize package versions (#14003 ) * Mark all blobs as shipping - available (though not discoverable) in public dotnetcli feed * Stabilize package versions * Remove assumption that Microsoft.AspNetCore.AzureAppServices.SiteExtension packages have same version - Microsoft.AspNetCore.AzureAppServices.SiteExtension.3.0 ships - Microsoft.AspNetCore.AzureAppServices.SiteExtension.3.0.x?? do not ship * Make installer versions consistent - VS.Redist.Common.AspNetCore.SharedFramework and ...TargetingPack packages are non-shipping - everything else ships nit: remove extra whitespace in .nuspec files for the packages * Correct assumptions in framework unit tests - tests sometimes do not calculate version properties as product projects do - Microsoft.AspNetCore.App.Ref and ...Runtime packages may rev versions separately * Fix last 2 `SharedFxTests` failures * Correct Microsoft.AspNetCore.App* versions used in ProjectTemplates tests - `$(SharedFxVersion)` is not useful in test projects due to stable versioning * Add continue on error for test templates		2019-09-15 13:34:08 -07:00
..
Web.Client.ItemTemplates	…
Web.ItemTemplates	…
Web.ProjectTemplates	Fixup Razor Class Library template namespace and component content (#13419 )	2019-08-27 16:00:39 -07:00
Web.Spa.ProjectTemplates	[ApiAuth] Update partner dependencies to their final versions (#13260 )	2019-09-07 02:39:47 +02:00
migrations	…
scripts	…
test	Stabilize package versions (#14003 )	2019-09-15 13:34:08 -07:00
testassets/DotNetToolsInstaller	…
.gitignore	…
Directory.Build.props	…
Directory.Build.targets	…
GenerateContent.targets	…
ProjectTemplates.sln	Remove stateful prerendering	2019-08-01 07:44:14 -07:00
ProjectTemplatesNoDeps.slnf	[ApiAuth] Switches back to use code+PKCE (#12375 )	2019-07-20 13:06:53 +02:00
README.md	…
THIRD-PARTY-NOTICES	…
TemplateProjects.props	…
build.cmd	…
build.sh	…
startvs.cmd	…
templates.nuspec	…

README.md

Templates

Getting Started

These are project templates which are used in .NET Core for creating ASP.NET Core applications.

Prerequisites

Some projects in this repository (like SignalR Java Client) require JDK installation and configuration of JAVA_HOME environment variable.

If you don't have the JDK installed, you can find it from https://www.oracle.com/technetwork/java/javase/downloads/index.html
After installation define a new environment variable named JAVA_HOME pointing to the root of the latest JDK installation (for Windows it will be something like c:\Program Files\Java\jdk-12).
Add the %JAVA_HOME%\bin directory to the PATH environment variable

Building Templates

Run . .\activate.ps1 if you haven't already.
Run git submodule update --init --recursive if you haven't already.
Run git submodule update to update submodules.
Run build.cmd -all -pack -configuration Release in the repository root to build all of the dependencies.
Run build.cmd -pack -NoRestore -NoBuilddeps -configuration Release in 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.App that was built during the previous step, it is NOT advised that you install templates created on your local machine via dotnet new -i [nupkgPath]. Instead, use the Run-[Template]-Locally.ps1 scripts in the script folder. These scripts do dotnet new -i with your packages, but also apply a series of fixes and tweaks to the created template which keep the fact that you don't have a production Microsoft.AspNetCore.App from 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".
Run .\build.cmd -test -NoRestore -NoBuild -NoBuilddeps -configuration Release "/p:RunTemplateTests=true" to run template tests.

** Note** Templating tests require Visual Studio unless a full build (CI) is performed.