Configuration file enhancements (#15574)
Luke Latham
GitHub
parent
c7bc61339a
commit
92c5d7a0dc
|
|
@ -5,7 +5,7 @@ description: Learn how to control app behavior across multiple environments in A
|
|||
monikerRange: '>= aspnetcore-2.1'
|
||||
ms.author: riande
|
||||
ms.custom: mvc
|
||||
ms.date: 11/05/2019
|
||||
ms.date: 11/07/2019
|
||||
uid: fundamentals/environments
|
||||
---
|
||||
# Use multiple environments in ASP.NET Core
|
||||
|
|
@ -256,7 +256,7 @@ To set the `ASPNETCORE_ENVIRONMENT` environment variable with *web.config*, see
|
|||
|
||||
**Project file or publish profile**
|
||||
|
||||
**For Windows IIS deployments:** Include the `<EnvironmentName>` property in the publish profile (*.pubxml*) or project file. This approach sets the environment in *web.config* when the project is published:
|
||||
**For Windows IIS deployments:** Include the `<EnvironmentName>` property in the [publish profile (.pubxml)](xref:host-and-deploy/visual-studio-publish-profiles) or project file. This approach sets the environment in *web.config* when the project is published:
|
||||
|
||||
```xml
|
||||
<PropertyGroup>
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ description: Discover the web servers Kestrel and HTTP.sys for ASP.NET Core. Lea
|
|||
monikerRange: '>= aspnetcore-2.1'
|
||||
ms.author: riande
|
||||
ms.custom: mvc
|
||||
ms.date: 08/10/2019
|
||||
ms.date: 11/07/2019
|
||||
uid: fundamentals/servers/index
|
||||
---
|
||||
# Web server implementations in ASP.NET Core
|
||||
|
|
@ -150,7 +150,9 @@ The server is launched when the Integrated Development Environment (IDE) or edit
|
|||
* [Visual Studio Code](https://code.visualstudio.com/) – The app and server are started by [Omnisharp](https://github.com/OmniSharp/omnisharp-vscode), which activates the CoreCLR debugger.
|
||||
* [Visual Studio for Mac](https://visualstudio.microsoft.com/vs/mac/) – The app and server are started by the [Mono Soft-Mode Debugger](https://www.mono-project.com/docs/advanced/runtime/docs/soft-debugger/).
|
||||
|
||||
When launching the app from a command prompt in the project's folder, [dotnet run](/dotnet/core/tools/dotnet-run) launches the app and server (Kestrel and HTTP.sys only). The configuration is specified by the `-c|--configuration` option, which is set to either `Debug` (default) or `Release`. If launch profiles are present in a *launchSettings.json* file, use the `--launch-profile <NAME>` option to set the launch profile (for example, `Development` or `Production`). For more information, see [dotnet run](/dotnet/core/tools/dotnet-run) and [.NET Core distribution packaging](/dotnet/core/build/distribution-packaging).
|
||||
When launching the app from a command prompt in the project's folder, [dotnet run](/dotnet/core/tools/dotnet-run) launches the app and server (Kestrel and HTTP.sys only). The configuration is specified by the `-c|--configuration` option, which is set to either `Debug` (default) or `Release`.
|
||||
|
||||
A *launchSettings.json* file provides configuration when launching an app with `dotnet run` or with a debugger built into tooling, such as Visual Studio. If launch profiles are present in a *launchSettings.json* file, use the `--launch-profile {PROFILE NAME}` option with the`dotnet run` command or select the profile in Visual Studio. For more information, see [dotnet run](/dotnet/core/tools/dotnet-run) and [.NET Core distribution packaging](/dotnet/core/build/distribution-packaging).
|
||||
|
||||
## HTTP/2 support
|
||||
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ description: Learn how to configure the ASP.NET Core Module for hosting ASP.NET
|
|||
monikerRange: '>= aspnetcore-2.1'
|
||||
ms.author: riande
|
||||
ms.custom: mvc
|
||||
ms.date: 10/24/2019
|
||||
ms.date: 11/07/2019
|
||||
uid: host-and-deploy/aspnet-core-module
|
||||
---
|
||||
# ASP.NET Core Module
|
||||
|
|
@ -202,7 +202,7 @@ The following example sets two environment variables in *web.config*. `ASPNETCOR
|
|||
```
|
||||
|
||||
> [!NOTE]
|
||||
> An alternative to setting the environment directly in *web.config* is to include the `<EnvironmentName>` property in the publish profile (*.pubxml*) or project file. This approach sets the environment in *web.config* when the project is published:
|
||||
> An alternative to setting the environment directly in *web.config* is to include the `<EnvironmentName>` property in the [publish profile (.pubxml)](xref:host-and-deploy/visual-studio-publish-profiles) or project file. This approach sets the environment in *web.config* when the project is published:
|
||||
>
|
||||
> ```xml
|
||||
> <PropertyGroup>
|
||||
|
|
@ -617,7 +617,7 @@ The following example sets two environment variables. `ASPNETCORE_ENVIRONMENT` c
|
|||
```
|
||||
|
||||
> [!NOTE]
|
||||
> An alternative to setting the environment directly in *web.config* is to include the `<EnvironmentName>` property in the publish profile (*.pubxml*) or project file. This approach sets the environment in *web.config* when the project is published:
|
||||
> An alternative to setting the environment directly in *web.config* is to include the `<EnvironmentName>` property in the [publish profile (.pubxml)](xref:host-and-deploy/visual-studio-publish-profiles) or project file. This approach sets the environment in *web.config* when the project is published:
|
||||
>
|
||||
> ```xml
|
||||
> <PropertyGroup>
|
||||
|
|
|
|||
|
|
@ -5,7 +5,7 @@ description: Learn how to set up hosting environments and deploy ASP.NET Core ap
|
|||
monikerRange: '>= aspnetcore-2.1'
|
||||
ms.author: riande
|
||||
ms.custom: mvc
|
||||
ms.date: 05/12/2019
|
||||
ms.date: 11/07/2019
|
||||
uid: host-and-deploy/index
|
||||
---
|
||||
# Host and deploy ASP.NET Core
|
||||
|
|
@ -63,6 +63,10 @@ See <xref:tutorials/publish-to-azure-webapp-using-vs> for instructions on how to
|
|||
|
||||
See <xref:host-and-deploy/visual-studio-publish-profiles> for instructions on how to publish an app with a Visual Studio publish profile, including from a Windows command prompt using the [dotnet msbuild](/dotnet/core/tools/dotnet-msbuild) command.
|
||||
|
||||
## Internet Information Services (IIS)
|
||||
|
||||
For deployments to Internet Information Services (IIS) with configuration provided by the *web.config* file, see the articles under <xref:host-and-deploy/iis/index>.
|
||||
|
||||
## Host in a web farm
|
||||
|
||||
For information on configuration for hosting ASP.NET Core apps in a web farm environment (for example, deployment of multiple instances of your app for scalability), see <xref:host-and-deploy/web-farm>.
|
||||
|
|
|
|||
|
|
@ -1,14 +1,14 @@
|
|||
---
|
||||
title: Visual Studio publish profiles for ASP.NET Core app deployment
|
||||
title: Visual Studio publish profiles (.pubxml) for ASP.NET Core app deployment
|
||||
author: rick-anderson
|
||||
description: Learn how to create publish profiles in Visual Studio and use them for managing ASP.NET Core app deployments to various targets.
|
||||
monikerRange: '>= aspnetcore-2.1'
|
||||
ms.author: riande
|
||||
ms.custom: mvc
|
||||
ms.date: 10/12/2019
|
||||
ms.date: 11/07/2019
|
||||
uid: host-and-deploy/visual-studio-publish-profiles
|
||||
---
|
||||
# Visual Studio publish profiles for ASP.NET Core app deployment
|
||||
# Visual Studio publish profiles (.pubxml) for ASP.NET Core app deployment
|
||||
|
||||
By [Sayed Ibrahim Hashimi](https://github.com/sayedihashimi) and [Rick Anderson](https://twitter.com/RickAndMSFT)
|
||||
|
||||
|
|
|
|||
Loading…
Reference in New Issue