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.
When a project is created with ExcludeLaunchSettings enabled, set the
NoDefaultLaunchSettingsFile property to prevent Visual Studio from
creating a launchSettings.json.
As discussed in aspnet/Home#3292, we're reversing course on the implicit package version feature. This adds a package version for Microsoft.AspNetCore.App to the `dotnet new` and VS templates.
This property is no longer needed because the Microsoft.AspNetCore.All and .App packages set the shared framework version. RuntimeFrameworkVersion is inferred by Microsoft.NET.Sdk
* Adds launchSettings.json to all of our templates.
* Provides an alternative flag to exclude it.
* Adds HTTPS support in launchSettings.json.
* Re-adds HTTPS redirect and HSTS middleware for C# templates.
* Improves some infrastructure aspects:
* Prefix all our test projects with AspNet.Template to allow easy
killing of orphaned processes.
* Setup an HTTPS certificate automatically for use with tests in the
same way our tooling does it on customers machines.
* Switch from OS selected ports to randomly selected ports. This is
required as we need to know the port to use for HTTPS.
* Allow disabling browser automation through an environment variable.
* Setup Firefox to allow untrusted certificates when using Selenium.
* Allow running Selenium tests on firefox by setting an environment
variable.
Changes:
- Replaces PackageLineup with the dependencies.props approach to manage package versions.
- Generate the csproj/fsproj files that go into template packages
- Remove the DependencyUpdater and PullRequestSubmitter tasks
- Remove bower.json and bowerrc from Microsoft.DotNet.Web.ProjectTemplates
- Set MyGet feeds via MSBuild instead of NuGet.config
- Upgrades to the functional tests
- Update Selenium
- Make it possible to run tests on macOS/linux
- Disable test parallelization
When the code lived in dotnet/templating, the 1.x, 2.0, and 2.1 templates all needed to sit side-by-side.
Now that this code builds from aspnet/templating, we're reorganizing the folder and branch structure to
match the aspnetcore runtime repos.
Branches:
rel/1.1.5 = Microsoft.DotNet.Web.ProjectTemplates.1.x
rel/2.0.3 = Microsoft.DotNet.Web.ProjectTemplates.2.0
dev = Microsoft.DotNet.Web.ProjectTemplates.2.1