Merge branch 'master' into composeEdits

Author: ucheNkadiCode

docker/tutorials/share-your-app.md

@@ -18,7 +18,7 @@ Now that we've built an image, let's share it! To share Docker images, you have
 
 To push an image, first, you need to create a repo on Docker Hub.
 
-1. Go to [Docker Hub](https://hub.docker.com) and log in if you need to.
+1. Go to [Docker Hub](https://hub.docker.com/signup/msftedge?utm_source=msftedge) and log in if you need to.
 
 1. Click the **Create Repository** button.
 
@@ -94,4 +94,4 @@ Now that you've that figured out, recall that at the end of the last section, wh
 Continue with the tutorial!
 
 > [!div class="nextstepaction"]
-> [Persisting your database](persist-your-data.md)
+> [Persisting your database](persist-your-data.md)

docker/tutorials/use-docker-compose.md

@@ -162,7 +162,7 @@ docker run -d \
         image: mysql:5.7
     ```
 
-1. Next, define the volume mapping. When you ran the container with `docker run`, the named volume was created automatically. However, that doesn't happen when running with Compose. You need to define the volume in the top-level `volumes:` section and then specify the mountpoint in the service config. By simply providing only the volume name, the default options are used. There are [many more options available](https://docs.docker.com/compose/compose-file/#volume-configuration-reference) though.
+1. Next, define the volume mapping. When you ran the container with `docker run`, the named volume was created automatically. However, that doesn't happen when running with Compose. You need to define the volume in the top-level `volumes:` section and then specify the mountpoint in the service config. By simply providing only the volume name, the default options are used. There are [many more options available](https://github.com/compose-spec/compose-spec/blob/master/spec.md#volumes-top-level-element) though.
 
     ```yaml hl_lines="8 9 10 11 12"
     version: "3.7"

docker/tutorials/your-application.md

@@ -24,7 +24,7 @@ Before you can run the application, you need to get the application source code
 
 1. Make sure that you have Docker for Windows or Docker Community Edition installed on the local machine. See [Docker for Windows installation documentation](https://docs.docker.com/docker-for-windows/install/). The install process makes the ZIP file containing the sample available at the localhost address.
 
-1. [Download the ZIP](http://localhost/assets/app.zip). Open the ZIP file and make sure you extract the contents.
+1. [Download the ZIP](https://github.com/docker/getting-started/tree/master/app). Open the ZIP file and make sure you extract the contents.
 
 1. Once extracted, use your favorite code editor to open the project. If you're in need of an editor, you can use [Visual Studio Code](https://code.visualstudio.com/). You should see the `package.json` and two subdirectories (`src` and `spec`).
 

docs/azure/cloud-services-extended-support.md

@@ -1,5 +1,5 @@
 ---
-title: Use Cloud Services (extended support) (Preview)
+title: Use Cloud Services (extended support)
 description: Learn now to create and deploy a Cloud Services (extended support) using Azure Resource Manager with Visual Studio
 author: ghogen
 manager: jmartens
@@ -10,26 +10,20 @@ ms.date: 01/25/2021
 ms.author: ghogen
 monikerRange: ">=vs-2019"
 ---
-# Create and deploy to Cloud Services (extended support) in Visual Studio (Preview)
+# Create and deploy to Cloud Services (extended support) in Visual Studio
 
-Starting with [Visual Studio 2019 version 16.9](https://visualstudio.microsoft.com/vs/preview) (currently in preview), you can work with cloud services by using Azure Resource Manager, which greatly simplifies and modernizes maintenance and management of Azure resources. This is enabled by a new Azure service referred to as *Cloud Services (extended support)*. You can publish an existing cloud service to Cloud Services (extended support). For information on this Azure service, see [Cloud Services (extended support) documentation](/azure/cloud-services-extended-support/overview).
+Starting with [Visual Studio 2019 version 16.9](https://visualstudio.microsoft.com/vs/), you can work with cloud services by using Azure Resource Manager, which greatly simplifies and modernizes maintenance and management of Azure resources. This is enabled by a new Azure service referred to as *Cloud Services (extended support)*. You can publish an existing cloud service to Cloud Services (extended support). For information on this Azure service, see [Cloud Services (extended support) documentation](/azure/cloud-services-extended-support/overview).
 
 ## Publish to Cloud Services (extended support)
 
-When you publish your existing Azure Cloud Service project to Cloud Services (extended support), you still retain the capability to publish to a classic Azure Cloud Service. In Visual Studio 2019 version 16.9 Preview 3 and later, classic cloud service projects have a special version of the **Publish** command, **Publish (extended support)**. This command appears on the shortcut menu in **Solution Explorer**.
+When you publish your existing Azure Cloud Service project to Cloud Services (extended support), you still retain the capability to publish to a classic Azure Cloud Service. In Visual Studio 2019 version 16.9 and later, classic cloud service projects have a special version of the **Publish** command, **Publish (extended support)**. This command appears on the shortcut menu in **Solution Explorer**.
 
-There are some differences when you publish to Cloud Services (extended support). For example, you are not asked if you are publishing to **Staging** or **Production**, because these deployment slots are not part of the extended support publishing model. Instead, with Cloud Services (extended support), you can set up multiple deployments, and swap deployments in the Azure portal. Although the Visual Studio tooling allows for setting this in 16.9 Preview 3, the swap feature will not be enabled until a later release of Cloud Services (extended support) and may result in a failure at deployment time during the Preview.
+There are some differences when you publish to Cloud Services (extended support). For example, you are not asked if you are publishing to **Staging** or **Production**, because these deployment slots are not part of the extended support publishing model. Instead, with Cloud Services (extended support), you can set up multiple deployments, and swap deployments in the Azure portal. Although the Visual Studio tooling allows for setting this in 16.9, the swap feature will not be enabled until a later release of Cloud Services (extended support) and may result in a failure at deployment time during the Preview.
 
 Before publishing a classic Azure Cloud Service to Cloud Services (extended support), check the storage accounts your project uses and make sure they are Storage V1 or Storage V2 accounts. The classic storage account types will fail with an error message at deploy time. Be sure to check the storage account used by diagnostics. To check the diagnostics storage account, see [Set up diagnostics for Azure Cloud Services and virtual machines](vs-azure-tools-diagnostics-for-cloud-services-and-virtual-machines.md). If your service uses a classic storage account, you can upgrade it; see [Upgrade to a general-purpose v2 storage account](/azure/storage/common/storage-account-upgrade?tabs=azure-portal).  For general information on the types of storage accounts, see [Storage account overview](/azure/storage/common/storage-account-overview).
 
 ### To publish a classic Azure Cloud Service project to Cloud Services (extended support)
 
-1. Cloud Services (extended support) is currently in preview. Register the feature for your subscription as follows:
-
-   ```azurepowershell-interactive
-   Register-AzProviderFeature -FeatureName CloudServices -ProviderNamespace Microsoft.Compute
-   ```
-
 1. Right-click on the project node in your Azure Cloud Service (classic) project and choose **Publish (extended support)...**. The **Publish wizard** opens at the first screen.
 
    ![Choose Publish (extended support) from the menu](./media/cloud-services-extended-support/publish-commands-on-menu.png)

docs/azure/index.yml

@@ -88,6 +88,8 @@ landingContent:
     linkLists:
     - linkListType: how-to-guide
       links:
+        - text: Create and deploy to Cloud Services (extended support)
+          url: cloud-services-extended-support.md
         - text: Create and configure Azure cloud service projects
           url: vs-azure-tools-azure-project-create.md
         - text: Debug cloud services locally and in Azure

docs/azure/media/cloud-services-extended-support/publish-commands-on-menu.png

@@ -40,7 +40,7 @@
   items:
   - name: Work with cloud service projects
     items:
-    - name: Use Cloud Services (extended support) (Preview)
+    - name: Use Cloud Services (extended support)
       href: cloud-services-extended-support.md
     - name: Create an Azure cloud service project
       href: vs-azure-tools-azure-project-create.md

docs/azure/toc.yml

@@ -1,4 +1,5 @@
 ---
+description: "An exception was raised within managed code analysis tool that does not indicate an expected error condition."
 title: CA0001
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0001.md

@@ -1,4 +1,5 @@
 ---
+description: "No rules were selected."
 title: CA0051
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0051.md

@@ -1,4 +1,5 @@
 ---
+description: "No targets were selected to analyze."
 title: CA0052
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0052.md

@@ -1,4 +1,5 @@
 ---
+description: "Rule assembly could not be loaded."
 title: CA0053
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0053.md

@@ -1,5 +1,6 @@
 ---
-title: CA0054
+title: "CA0054: Custom rule assembly has invalid XML resources."
+description: "This occurs if a custom rule assembly has invalid XML resources describing its rules."
 ms.date: 10/19/2016
 ms.topic: reference
 f1_keywords:
@@ -14,7 +15,7 @@ ms.workload:
   - "multiple"
 ---
 # CA0054
-Custom rule assembly has invalid XML resources
+Custom rule assembly has invalid XML resources.
 
 This occurs if a custom rule assembly has invalid XML resources describing its rules. The correct format is as follows:
 

docs/code-quality/ca0054.md

@@ -1,5 +1,6 @@
 ---
-title: CA0055
+title: "CA0055: Could not load file"
+description: "The code analysis tool was unable to load the target file that was specified for analysis."
 ms.date: 10/20/2016
 ms.topic: reference
 f1_keywords:
@@ -14,7 +15,8 @@ ms.workload:
 - multiple
 ---
 # CA0055
-Could not load file:\<path>
+
+Could not load file
 
 The code analysis tool was unable to load the target file that was specified for analysis. This occurs if the file is not found or access to the file was denied. Typically, this occurs if the user chose to override the input assembly property in Visual Studio, or invoked fxcopcmd.exe manually.
 

docs/code-quality/ca0055.md

@@ -1,4 +1,5 @@
 ---
+description: "A project file has an incorrect version of the analysis tool."
 title: CA0056
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0056.md

@@ -1,5 +1,6 @@
 ---
-title: CA0057
+title: "CA0057: Violations cannot be mapped to the current set of targets and rules"
+description: "This error occurs if FxCopCmd.exe is invoked manually with a project file or an imported XML report that has violations that cannot be mapped to the current set of targets and rules."
 ms.date: 10/19/2016
 ms.topic: reference
 f1_keywords:
@@ -14,6 +15,7 @@ ms.workload:
   - "multiple"
 ---
 # CA0057
+
 Violations cannot be mapped to the current set of targets and rules
 
 This error occurs if FxCopCmd.exe is invoked manually with a project file or an /imported XML report that has violations that cannot be mapped to the current set of targets and rules.

docs/code-quality/ca0057.md

@@ -1,4 +1,5 @@
 ---
+description: "Unable to load assemblies referenced."
 title: CA0058
 ms.date: 10/20/2016
 ms.topic: reference

docs/code-quality/ca0058.md

@@ -1,4 +1,5 @@
 ---
+description: "Command line switch error."
 title: CA0059
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0059.md

@@ -1,4 +1,5 @@
 ---
+description: "Unable to load assemblies referenced indirectly."
 title: CA0060
 ms.date: 10/20/2016
 ms.topic: reference

docs/code-quality/ca0060.md

@@ -1,4 +1,5 @@
 ---
+description: "The rule 'RuleId' could not be found."
 title: CA0061
 ms.date: 10/20/2016
 ms.topic: reference

docs/code-quality/ca0061.md

@@ -1,4 +1,5 @@
 ---
+description: "The rule 'RuleId' referenced in rule set '*RuleSetName*' could not be found."
 title: CA0062
 ms.date: 10/20/2016
 ms.topic: reference

docs/code-quality/ca0062.md

@@ -1,4 +1,5 @@
 ---
+description: "Failed to load rule set file or one of its dependent rule set files."
 title: CA0063
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0063.md

@@ -1,4 +1,5 @@
 ---
+description: "No analysis was performed because the specified rule set did not contain any FxCop rules."
 title: CA0064
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0064.md

@@ -1,5 +1,6 @@
 ---
-title: CA0065
+title: 'CA0065: Unsupported metadata construct'
+description: "Type 'TypeName' contains both a property and a field with the same name 'PropertyFieldName'."
 ms.date: 10/19/2016
 ms.topic: reference
 ms.assetid: 53ead5cf-46c7-4dfb-9cd3-10cb90cc722c
@@ -10,7 +11,10 @@ ms.workload:
   - "multiple"
 ---
 # CA0065
-Unsupported metadata construct: Type '*TypeName*' contains both a property and a field with the same name '*PropertyFieldName*'
+
+Unsupported metadata construct
+
+Type '*TypeName*' contains both a property and a field with the same name '*PropertyFieldName*'.
 
 ## See also
 [Code Analysis Application Errors](../code-quality/code-analysis-application-errors.md)

docs/code-quality/ca0065.md

@@ -1,4 +1,5 @@
 ---
+description: "The value 'VersionID' provided to the /targetframeworkversion is not a recognized version."
 title: CA0066
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0066.md

@@ -1,4 +1,5 @@
 ---
+description: "Directory not found."
 title: CA0067
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0067.md

@@ -1,4 +1,5 @@
 ---
+description: "Debug information (symbols) could not be found for target assembly 'AssemblyName'."
 title: CA0068
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0068.md

@@ -1,4 +1,5 @@
 ---
+description: "UsingAlternatePlatform."
 title: CA0069
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0069.md

@@ -1,5 +1,6 @@
 ---
-title: CA0501
+title: 'CA0501: Unable to read output report'
+description: "This occurs when output report cannot be written, either because the disk is full, permissions are insufficient, or the directory does not exist."
 ms.date: 10/19/2016
 ms.topic: reference
 f1_keywords:
@@ -14,6 +15,7 @@ ms.workload:
 - multiple
 ---
 # CA0501
+
 Unable to read output report
 
 This occurs when output report cannot be written because of one of the following reasons:

docs/code-quality/ca0501.md

@@ -1,5 +1,6 @@
 ---
-title: CA0502
+title: 'CA0502: Unsupported language'
+description: "This error occurs when the user tries to analyze an ASP.NET project that contains one or more pages or classes written in a language other than C# or Visual Basic."
 ms.date: 10/19/2016
 ms.topic: reference
 f1_keywords:
@@ -14,6 +15,7 @@ ms.workload:
   - "multiple"
 ---
 # CA0502
+
 Unsupported language
 
 This error occurs when the user tries to analyze an ASP.NET project that contains one or more pages or classes written in a language other than C# or Visual Basic. To fix this error, remove the file from the project or disable code analysis.

docs/code-quality/ca0502.md

@@ -1,5 +1,6 @@
 ---
-title: CA0503
+title: 'CA0503: The property is deprecated. Use the superceding property'
+description: "Generated when a deprecated code analysis property contains a value in the build or project configuration file."
 ms.date: 10/19/2016
 ms.topic: reference
 f1_keywords:
@@ -12,7 +13,8 @@ ms.workload:
 - multiple
 ---
 # CA0503
-The property is deprecated. Use the superseding property
+
+The property is deprecated. Use the superceding property
 
 Warning CA0503 is generated when a deprecated code analysis property contains a value in the build or project configuration file. To resolve this warning, use the specified property that supersedes it.
 

docs/code-quality/ca0503.md

@@ -1,5 +1,6 @@
 ---
-title: CA0504
+title: 'CA0504: Rule directory was ignored because it does not exist.'
+description: "Generated when a directory specified in the CodeAnalysisRuleDirectories property in a project or build configuration file could not be found."
 ms.date: 10/19/2016
 ms.topic: reference
 f1_keywords:
@@ -12,6 +13,7 @@ ms.workload:
   - "multiple"
 ---
 # CA0504
+
 Rule directory was ignored because it does not exist
 
 Warning CA504 is generated when a directory specified in the **CodeAnalysisRuleDirectories** property in a project or build configuration file could not be found. To resolve this issue, enter a valid directory path.

docs/code-quality/ca0504.md

@@ -1,4 +1,5 @@
 ---
+description: "The deprecated property will be ignored because the superceding property is defined."
 title: CA0505
 ms.date: 10/19/2016
 ms.topic: reference

docs/code-quality/ca0505.md

@@ -1,4 +1,5 @@
 ---
+description: "The parameter signature of an externally visible generic method does not contain types that correspond to all the type parameters of the method."
 title: 'CA1004: Generic methods should provide type parameter'
 ms.date: 11/04/2016
 ms.topic: reference

docs/code-quality/ca1004.md

@@ -1,4 +1,5 @@
 ---
+description: "An externally visible member has a signature that contains a nested type argument."
 title: 'CA1006: Do not nest generic types in member signatures'
 ms.date: 11/04/2016
 ms.topic: reference
@@ -41,8 +42,8 @@ Do not suppress a warning from this rule. Providing generics in a syntax that is
 ## Example
 The following example shows a method that violates the rule and the syntax that is required to call the violating method.
 
-[!code-vb[FxCop.Design.NestedGenerics#1](../code-quality/codesnippet/VisualBasic/ca1006-do-not-nest-generic-types-in-member-signatures_1.vb)]
-[!code-csharp[FxCop.Design.NestedGenerics#1](../code-quality/codesnippet/CSharp/ca1006-do-not-nest-generic-types-in-member-signatures_1.cs)]
+:::code language="vb" source="../snippets/visualbasic/VS_Snippets_CodeAnalysis/FxCop.Design.NestedGenerics/vb/FxCop.Design.NestedGenerics.vb" id="Snippet1":::
+:::code language="csharp" source="../snippets/csharp/VS_Snippets_CodeAnalysis/FxCop.Design.NestedGenerics/cs/FxCop.Design.NestedGenerics.cs" id="Snippet1":::
 
 ## Related rules
 [CA1005: Avoid excessive parameters on generic types](/dotnet/fundamentals/code-analysis/quality-rules/ca1005)

docs/code-quality/ca1006.md

@@ -1,5 +1,6 @@
 ---
 title: 'CA1007: Use generics where appropriate'
+description: "An externally visible method contains a reference parameter of type System.Object, and the containing assembly targets .NET Framework 2.0."
 ms.date: 11/04/2016
 ms.topic: reference
 f1_keywords:
@@ -41,8 +42,8 @@ Do not suppress a warning from this rule.
 ## Example
 The following example shows a general-purpose swap routine that is implemented as both nongeneric and generic methods. Note how efficiently the strings are swapped by using the generic method compared to the nongeneric method.
 
-[!code-vb[FxCop.Design.UseGenerics#1](../code-quality/codesnippet/VisualBasic/ca1007-use-generics-where-appropriate_1.vb)]
-[!code-csharp[FxCop.Design.UseGenerics#1](../code-quality/codesnippet/CSharp/ca1007-use-generics-where-appropriate_1.cs)]
+:::code language="vb" source="../snippets/visualbasic/VS_Snippets_CodeAnalysis/FxCop.Design.UseGenerics/vb/FxCop.Design.UseGenerics.vb" id="Snippet1":::
+:::code language="csharp" source="../snippets/csharp/VS_Snippets_CodeAnalysis/FxCop.Design.UseGenerics/cs/FxCop.Design.UseGenerics.cs" id="Snippet1":::
 
 ## Related rules
 [CA1005: Avoid excessive parameters on generic types](/dotnet/fundamentals/code-analysis/quality-rules/ca1005)