From fbf119dcd9631edf1d7189125ed2779607a10be0 Mon Sep 17 00:00:00 2001 From: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com> Date: Wed, 13 Jan 2021 15:47:37 -1000 Subject: [PATCH] Update pub to Azure (#20830) --- .../host-and-deploy/azure-apps/index.md | 50 +++++++++++-------- 1 file changed, 29 insertions(+), 21 deletions(-) diff --git a/aspnetcore/host-and-deploy/azure-apps/index.md b/aspnetcore/host-and-deploy/azure-apps/index.md index 07350b9e5e..17f801d0e9 100644 --- a/aspnetcore/host-and-deploy/azure-apps/index.md +++ b/aspnetcore/host-and-deploy/azure-apps/index.md @@ -5,7 +5,7 @@ description: This article contains links to Azure host and deploy resources. monikerRange: '>= aspnetcore-2.1' ms.author: bradyg ms.custom: mvc -ms.date: 12/16/2019 +ms.date: 11/6/2020 no-loc: [appsettings.json, "ASP.NET Core Identity", cookie, Cookie, Blazor, "Blazor Server", "Blazor WebAssembly", "Identity", "Let's Encrypt", Razor, SignalR] uid: host-and-deploy/azure-apps/index --- @@ -68,7 +68,7 @@ For more information on .NET Core framework components and distribution methods, Include the following NuGet packages to provide automatic logging features for apps deployed to Azure App Service: -* [Microsoft.AspNetCore.AzureAppServices.HostingStartup](https://www.nuget.org/packages/Microsoft.AspNetCore.AzureAppServices.HostingStartup/) uses [IHostingStartup](xref:fundamentals/configuration/platform-specific-configuration) to provide ASP.NET Core light-up integration with Azure App Service. The added logging features are provided by the `Microsoft.AspNetCore.AzureAppServicesIntegration` package. +* [Microsoft.AspNetCore.AzureAppServices.HostingStartup](https://www.nuget.org/packages/Microsoft.AspNetCore.AzureAppServices.HostingStartup/) uses [IHostingStartup](xref:fundamentals/configuration/platform-specific-configuration) to provide ASP.NET Core logging integration with Azure App Service. The added logging features are provided by the `Microsoft.AspNetCore.AzureAppServicesIntegration` package. * [Microsoft.AspNetCore.AzureAppServicesIntegration](https://www.nuget.org/packages/Microsoft.AspNetCore.AzureAppServicesIntegration/) executes [AddAzureWebAppDiagnostics](/dotnet/api/microsoft.extensions.logging.azureappservicesloggerfactoryextensions.addazurewebappdiagnostics) to add Azure App Service diagnostics logging providers in the `Microsoft.Extensions.Logging.AzureAppServices` package. * [Microsoft.Extensions.Logging.AzureAppServices](https://www.nuget.org/packages/Microsoft.Extensions.Logging.AzureAppServices/) provides logger implementations to support Azure App Service diagnostics logs and log streaming features. @@ -255,16 +255,20 @@ For a 64-bit deployment: # [Visual Studio](#tab/visual-studio) -1. Select **Build** > **Publish {Application Name}** from the Visual Studio toolbar or right-click the project in **Solution Explorer** and select **Publish**. -1. In the **Pick a publish target** dialog, confirm that **App Service** is selected. +1. Right-click the project in **Solution Explorer** and select **Publish**. Alternatively, select **Build** > **Publish {Application Name}** from the Visual Studio toolbar. +1. In the **Publish** dialog, select **Azure** > **Next**. +1. Select the Azure service. 1. Select **Advanced**. The **Publish** dialog opens. -1. In the **Publish** dialog: - * Confirm that the **Release** configuration is selected. - * Open the **Deployment Mode** drop-down list and select **Framework-Dependent**. - * Select **Portable** as the **Target Runtime**. - * If you need to remove additional files upon deployment, open **File Publish Options** and select the check box to remove additional files at the destination. +1. Select a Resource group and Hosting plan, or create new ones. +1. Select **Finish**. +1. In the **Publish** page: + * For **Configuration**, select the pen icon **Edit Configuration**: + * Confirm that the **Release** configuration is selected. + * In the **Deployment Mode** drop-down list, select **Framework-Dependent**. + * In the **Target Runtime** drop-down list, select the desired runtime. The default is `win-x86`. + * To remove additional files upon deployment, open **File Publish Options** and select the check box to remove additional files at the destination. * Select **Save**. -1. Create a new site or update an existing site by following the remaining prompts of the publish wizard. + * Select **Publish**. # [.NET Core CLI](#tab/netcore-cli/) @@ -286,20 +290,24 @@ Use Visual Studio or the .NET Core CLI for a [self-contained deployment (SCD)](/ # [Visual Studio](#tab/visual-studio) -1. Select **Build** > **Publish {Application Name}** from the Visual Studio toolbar or right-click the project in **Solution Explorer** and select **Publish**. -1. In the **Pick a publish target** dialog, confirm that **App Service** is selected. +1. Right-click the project in **Solution Explorer** and select **Publish**. Alternatively, select **Build** > **Publish {Application Name}** from the Visual Studio toolbar. +1. In the **Publish** dialog, select **Azure** > **Next**. +1. Select the Azure service. 1. Select **Advanced**. The **Publish** dialog opens. -1. In the **Publish** dialog: - * Confirm that the **Release** configuration is selected. - * Open the **Deployment Mode** drop-down list and select **Self-Contained**. - * Select the target runtime from the **Target Runtime** drop-down list. The default is `win-x86`. - * If you need to remove additional files upon deployment, open **File Publish Options** and select the check box to remove additional files at the destination. +1. Select a Resource group and Hosting plan, or create new ones. +1. Select **Finish**. +1. In the **Publish** page: + * For **Configuration**, select the pen icon **Edit Configuration**: + * Confirm that the **Release** configuration is selected. + * In the **Deployment Mode** drop-down list, select **Self-Contained**. + * In the **Target Runtime** drop-down list, select the desired runtime. The default is `win-x86`. + * To remove additional files upon deployment, open **File Publish Options** and select the check box to remove additional files at the destination. * Select **Save**. -1. Create a new site or update an existing site by following the remaining prompts of the publish wizard. + * Select **Publish**. # [.NET Core CLI](#tab/netcore-cli/) -1. In the project file, specify one or more [Runtime Identifiers (RIDs)](/dotnet/core/rid-catalog). Use `` (singular) for a single RID, or use `` (plural) to provide a semicolon-delimited list of RIDs. In the following example, the `win-x86` RID is specified: +1. In the project file, specify one or more [Runtime Identifiers (RIDs)](/dotnet/core/rid-catalog). Use `` for a single RID, or use `` to provide a semicolon-delimited list of multiple RIDs. In the following example, the `win-x86` RID is specified: ```xml @@ -314,13 +322,13 @@ Use Visual Studio or the .NET Core CLI for a [self-contained deployment (SCD)](/ dotnet publish --configuration Release --runtime win-x86 --self-contained ``` -1. Move the contents of the *bin/Release/{TARGET FRAMEWORK}/{RUNTIME IDENTIFIER}/publish* directory to the site in App Service. If dragging the *publish* folder contents from your local hard drive or network share directly to App Service in the Kudu console, drag the files to the `D:\home\site\wwwroot` folder in the Kudu console. +1. Move the contents of the *bin/Release/{TARGET FRAMEWORK}/{RUNTIME IDENTIFIER}/publish* directory to the site in App Service. If dragging the *publish* folder contents from your local hard drive or network share directly to App Service in the [Kudu console](https://github.com/projectkudu/kudu/wiki), drag the files to the `D:\home\site\wwwroot` folder in the Kudu console. --- ## Protocol settings (HTTPS) -Secure protocol bindings allow you specify a certificate to use when responding to requests over HTTPS. Binding requires a valid private certificate (*.pfx*) issued for the specific hostname. For more information, see [Tutorial: Bind an existing custom SSL certificate to Azure App Service](/azure/app-service/app-service-web-tutorial-custom-ssl). +Secure protocol bindings allow specifying a certificate to use when responding to requests over HTTPS. Binding requires a valid private certificate (*.pfx*) issued for the specific hostname. For more information, see [Tutorial: Bind an existing custom SSL certificate to Azure App Service](/azure/app-service/app-service-web-tutorial-custom-ssl). ## Transform web.config