Merge pull request #12241 from MicrosoftDocs/learn-build-service-prodbot/docutune-autopr-20240229-220038-2503359-ignore-build

[BULK] [DocuTune-Remediation] - Scheduled execution to fix known issues in Visual Studio documentation (part 3)

Author: ghogen

docs/azure/vs-azure-tools-cloud-service-project-managing-roles.md

@@ -1,14 +1,15 @@
 ---
-title: Managing roles in Azure cloud services
-description: Learn how to add and remove roles in Azure cloud services with Visual Studio.
+title: Managing roles in Azure Cloud Services
+description: Learn how to add and remove roles in Azure Cloud Services with Visual Studio.
 author: ghogen
 manager: jmartens
 ms.subservice: azure-development
 ms.topic: how-to
 ms.date: 03/21/2017
 ms.author: ghogen
 ---
-# Managing roles in Azure cloud services with Visual Studio
+
+# Managing roles in Azure Cloud Services with Visual Studio
 
  [!INCLUDE [Cloud Services](./includes/cloud-services-legacy.md)]
 
@@ -19,6 +20,7 @@ After you have created your Azure cloud service, you can add new roles to it or
 - [!INCLUDE [prerequisites-azure-subscription](includes/prerequisites-azure-subscription.md)]
 
 ## Adding a role to an Azure cloud service
+
 The following steps guide you through adding a web or worker role to an Azure cloud service project in Visual Studio.
 
 1. Create or open an Azure cloud service project in Visual Studio.
@@ -30,6 +32,7 @@ The following steps guide you through adding a web or worker role to an Azure cl
    ![Menu options to add a role to an Azure cloud service project](./media/vs-azure-tools-cloud-service-project-managing-roles/add-role.png)
 
 ## Removing a role from an Azure cloud service
+
 The following steps guide you through removing a web or worker role from an Azure cloud service project in Visual Studio.
 
 1. Create or open an Azure cloud service project in Visual Studio.
@@ -43,6 +46,7 @@ The following steps guide you through removing a web or worker role from an Azur
    ![Menu options to add a role to an Azure cloud service](./media/vs-azure-tools-cloud-service-project-managing-roles/remove-role.png)
 
 ## Readding a role to an Azure cloud service project
+
 If you remove a role from your cloud service project but later decide to add the role back to the project, only the role declaration and basic attributes, such as endpoints and diagnostics information, are added. No additional resources or references are added to the `ServiceDefinition.csdef` file or to the `ServiceConfiguration.cscfg` file. If you want to add this information, you need to manually add it back into these files.
 
 For example, you might remove a web service role and later you decide to add this role back into your solution. If you do this, an error occurs. To prevent this error, you have to add the `<LocalResources>` element shown in the following XML back into the `ServiceDefinition.csdef` file. Use the name of the web service role that you added back into the project as part of the name attribute for the **\<LocalStorage>** element. In this example, the name of the web service role is **WCFServiceWebRole1**.
@@ -69,4 +73,5 @@ For example, you might remove a web service role and later you decide to add thi
 ```
 
 ## Related content
+
 - [Configure the Roles for an Azure cloud service with Visual Studio](vs-azure-tools-configure-roles-for-cloud-service.md)

docs/azure/vs-azure-tools-cloud-service-publish-set-up-required-services-in-visual-studio.md

@@ -8,14 +8,15 @@ ms.topic: how-to
 ms.date: 11/10/2017
 ms.author: ghogen
 ---
+
 # Prepare to publish or deploy a cloud service from Visual Studio
 
  [!INCLUDE [Cloud Services](./includes/cloud-services-legacy.md)]
 
 To publish a cloud service project, you must set up the following services as described in this article:
 
-* A **cloud service** to run your roles in the Azure environment, and
-* A **storage account** that provides access to the Blob, Queue, and Table services.
+- A **cloud service** to run your roles in the Azure environment, and
+- A **storage account** that provides access to the Blob, Queue, and Table services.
 
 ## Prerequisites
 
@@ -71,7 +72,7 @@ To configure settings manually, use the property pages in Visual Studio for the
 
 ### About access keys
 
-The Azure portal shows the URLs that you can use to access resources in each of the Azure storage services, and also the primary and secondary access keys for your account. You use these keys to authenticate requests made against the storage services.
+The Azure portal shows the URLs that you can use to access resources in each of the Azure Storage services, and also the primary and secondary access keys for your account. You use these keys to authenticate requests made against the storage services.
 
 The secondary access key provides the same access to your storage account as the primary access key and is generated as a backup should your primary access key be compromised. Additionally, it is recommended that you regenerate your access keys on a regular basis. You can modify a connection string setting to use the secondary key while you regenerate the primary key, then you can modify it to use the regenerated primary key while you regenerate the secondary key.
 

docs/azure/vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address.md

@@ -8,22 +8,25 @@ ms.topic: how-to
 ms.date: 03/21/2017
 ms.author: ghogen
 ---
+
 # Retain a constant virtual IP address for an Azure cloud service
 
  [!INCLUDE [Cloud Services](./includes/cloud-services-legacy.md)]
 
-When you update a cloud service that's hosted in Azure, you might need to ensure that the virtual IP address (VIP) of the service doesn't change. Many domain management services use the Domain Name System (DNS) for registering domain names. DNS works only if the VIP remains the same. You can use the **Publish Wizard** in Azure Tools to ensure that the VIP of your cloud service doesn’t change when you update it. For more information about how to use DNS domain management for cloud services, see [Configuring a custom domain name for an Azure cloud service](/azure/cloud-services/cloud-services-custom-domain-name-portal).
+When you update a cloud service that's hosted in Azure, you might need to ensure that the virtual IP (VIP) address (VIP) of the service doesn't change. Many domain management services use the Domain Name System (DNS) for registering domain names. DNS works only if the VIP remains the same. You can use the **Publish Wizard** in Azure Tools to ensure that the VIP of your cloud service doesn't change when you update it. For more information about how to use DNS domain management for cloud services, see [Configuring a custom domain name for an Azure cloud service](/azure/cloud-services/cloud-services-custom-domain-name-portal).
 
 ## Prerequisites
 
 - [!INCLUDE [prerequisites-azure-subscription](includes/prerequisites-azure-subscription.md)]
 
 ## Publish a cloud service without changing its VIP
-The VIP of a cloud service is allocated when you first deploy it to Azure in a particular environment, such as the production environment. The VIP changes only if you delete the deployment explicitly or the deployment is implicitly deleted by the deployment update process. To retain the VIP, you must not delete your deployment, and you must make sure that Visual Studio doesn’t delete your deployment automatically.
+
+The VIP of a cloud service is allocated when you first deploy it to Azure in a particular environment, such as the production environment. The VIP changes only if you delete the deployment explicitly or the deployment is implicitly deleted by the deployment update process. To retain the VIP, you must not delete your deployment, and you must make sure that Visual Studio doesn't delete your deployment automatically.
 
 You can specify deployment settings in the **Publish Wizard**, which supports several deployment options. You can specify a fresh deployment or an update deployment, which can be incremental or simultaneous. Both kinds of update deployment retain the VIP. For definitions of these different types of deployment, see [Publish Azure Application Wizard](vs-azure-tools-publish-azure-application-wizard.md). In addition, you can control whether the previous deployment of a cloud service is deleted if an error occurs. If you don't set that option correctly, the VIP might change unexpectedly.
 
 ## Update a cloud service without changing its VIP
+
 1. Create or open an Azure cloud service project in Visual Studio.
 
 2. In **Solution Explorer**, right-click the project. On the shortcut menu, select **Publish**.
@@ -34,11 +37,11 @@ You can specify deployment settings in the **Publish Wizard**, which supports se
 
     ![Publish Azure Application Sign In page](./media/vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address/azure-publish-signin.png)
 
-4. On the **Common Settings** tab, verify that the name of the cloud service to which you’re deploying, the **Environment**, the **Build configuration**, and the **Service configuration** are all correct.
+4. On the **Common Settings** tab, verify that the name of the cloud service to which you're deploying, the **Environment**, the **Build configuration**, and the **Service configuration** are all correct.
 
     ![Publish Azure Application Common Settings tab](./media/vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address/azure-publish-common-settings.png)
 
-5. On the **Advanced Settings** tab, verify that the **Deployment label** and the **Storage account** are correct. Verify that the **Delete deployment on failure** check box is cleared, and verify that the **Deployment update** check box is selected. By clearing the **Delete deployment on failure** check box, you ensure that your VIP isn't lost if an error occurs during deployment. By selecting the **Deployment update** check box, you ensure that your deployment isn't deleted and your VIP isn't lost when you republish your application.
+5. On the **Advanced Settings** tab, verify that the **Deployment label** and the **Storage account** are correct. Verify that the **Delete deployment on failure** checkbox is cleared, and verify that the **Deployment update** checkbox is selected. By clearing the **Delete deployment on failure** checkbox, you ensure that your VIP isn't lost if an error occurs during deployment. By selecting the **Deployment update** checkbox, you ensure that your deployment isn't deleted and your VIP isn't lost when you republish your application.
 
     ![Publish Azure Application Advanced Settings tab](./media/vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address/azure-publish-advanced-settings.png)
 
@@ -51,4 +54,5 @@ You can specify deployment settings in the **Publish Wizard**, which supports se
     ![Publish Azure Application Summary page](./media/vs-azure-tools-cloud-service-retain-a-constant-virtual-ip-address/azure-publish-summary.png)
 
 ## Related content
+
 - [Using the Visual Studio Publish Azure Application Wizard](vs-azure-tools-publish-azure-application-wizard.md)

docs/azure/vs-azure-tools-command-line-build.md

@@ -8,6 +8,7 @@ ms.topic: how-to
 ms.date: 03/05/2017
 ms.author: ghogen
 ---
+
 # Building Azure projects from the command line
 
  [!INCLUDE [Cloud Services](./includes/cloud-services-legacy.md)]
@@ -17,14 +18,16 @@ Using the Microsoft Build Engine (MSBuild), you can build products in build-lab
 You can also run MSBuild at the command line, and this topic describes that approach. By setting properties on the command line, you can build specific configurations of a project. Similarly, you can also define the targets that MSBuild builds. For more information about command-line parameters and MSBuild, see [MSBuild Command-Line Reference](../msbuild/msbuild-command-line-reference.md).
 
 ## MSBuild parameters
+
 The simplest way to create a package is to run MSBuild with the `/t:Publish` option. By default, this command creates a directory in relation to the root folder for the project, such as `<ProjectDirectory>\bin\Configuration\app.publish\`. When you build an Azure project, two files are generated: the package file itself and the accompanying configuration file:
 
-* Package File (`project.cspkg`)
-* Configuration File (`ServiceConfiguration.TargetProfile.cscfg`)
+- Package File (`project.cspkg`)
+- Configuration File (`ServiceConfiguration.TargetProfile.cscfg`)
 
 By default, each Azure project includes one service-configuration file for local (debugging) builds and another for cloud (staging or production) builds. However, you can add or remove service-configuration files as needed. When you build a package within Visual Studio, you are asked which service-configuration file to include alongside the package. When you build a package by using MSBuild, the local service-configuration file is included by default. To include a different service-configuration file, set the `TargetProfile` property of the MSBuild command (`MSBuild /t:Publish /p:TargetProfile=ProfileName`).
 
 If you want to use an alternate directory for the stored package and configuration files, set the path by using the `/p:PublishDir=Directory\` option, including the trailing backslash separator.
 
 ## Related content
+
 After the package is built, you can deploy it to Azure.