huahaofeng
/
aspnetcore
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
aspnetcore/src/ProjectTemplates
History
Javier Calvarro Nelson 143c101693
[Identity] Move to use static web assets support. (#11029) 
* Moves Identity UI to use Static Web Assets
  * Removes the static files as embedded content.
  * Stops plugging the static assets through the embedded file provider.
  * Selects the UI framework at build time instead of runtime.
 		2019-07-25 17:34:45 +02:00
..
Web.Client.ItemTemplates Replace Internal.AspNetCore.Sdk with Microsoft.DotNet.Arcade.Sdk (#10674) 2019-06-07 17:19:41 -07:00
Web.ItemTemplates gRPC template updates (#11473) 2019-06-27 15:04:01 -07:00
Web.ProjectTemplates Make server-side Blazor template logout use POST. Fixes #11981 (#12419) 2019-07-21 17:20:46 -07:00
Web.Spa.ProjectTemplates [ApiAuth] Switches back to use code+PKCE (#12375) 2019-07-20 13:06:53 +02:00
migrations
…
scripts rename RazorComponents project 2019-07-12 08:48:56 -04:00
test [Identity] Move to use static web assets support. (#11029) 2019-07-25 17:34:45 +02:00
testassets/DotNetToolsInstaller
…
.gitignore
…
Directory.Build.props Add reference assemblies support (#7764) 2019-02-21 14:33:35 -08:00
Directory.Build.targets Replace Internal.AspNetCore.Sdk with Microsoft.DotNet.Arcade.Sdk (#10674) 2019-06-07 17:19:41 -07:00
GenerateContent.targets Replace Internal.AspNetCore.Sdk with Microsoft.DotNet.Arcade.Sdk (#10674) 2019-06-07 17:19:41 -07:00
ProjectTemplates.sln Rename .Components.Browser -> Components.Web 2019-07-01 15:36:35 -07:00
ProjectTemplatesNoDeps.slnf [ApiAuth] Switches back to use code+PKCE (#12375) 2019-07-20 13:06:53 +02:00
README.md Improvements to building templates locally (#12022) 2019-07-11 15:02:51 -07:00
THIRD-PARTY-NOTICES Added Angular v8 license notice (#12359) 2019-07-19 09:59:39 -07:00
TemplateProjects.props Replace Internal.AspNetCore.Sdk with Microsoft.DotNet.Arcade.Sdk (#10674) 2019-06-07 17:19:41 -07:00
build.cmd Improvements to building templates locally (#12022) 2019-07-11 15:02:51 -07:00
build.sh Enforce E2E test prerequisites when building individual solutions only (#11642) 2019-06-29 01:04:36 +02:00
startvs.cmd Mark flaky Angular test (#9926) 2019-05-02 10:28:11 -07:00
templates.nuspec Replace Internal.AspNetCore.Sdk with Microsoft.DotNet.Arcade.Sdk (#10674) 2019-06-07 17:19:41 -07:00

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.

  1. If you don't have the JDK installed, you can find it from https://www.oracle.com/technetwork/java/javase/downloads/index.html
  2. 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).
  3. Add the %JAVA_HOME%\bin directory to the PATH environment variable

Building Templates

  1. Run . .\activate.ps1 if you haven't already.

  2. Run git submodule update --init --recursive if you haven't already.

  3. Run git submodule update to update submodules.

  4. Run build.cmd -all -pack -configuration Release in the repository root to build all of the dependencies.

  5. Run build.cmd -pack -NoRestore -NoBuilddeps -configuration Release in this directory will produce NuGet packages for each class of template in the artifacts directory.

  6. 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.

  7. The ASP.NET localhost development certificate must also be installed and trusted or else you'll get a test error "Certificate error: Navigation blocked".

  8. 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.