Merge pull request #10310 from MicrosoftDocs/main638566887463002279sync_temp

learn-build-service-prod[bot] · web-flow · commit f64f775a1eb9 · 2024-07-16T01:06:01.000Z
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
diff --git a/docs/code-quality/ca0001.md b/docs/code-quality/ca0001.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0001
diff --git a/docs/code-quality/ca0051.md b/docs/code-quality/ca0051.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0051
diff --git a/docs/code-quality/ca0052.md b/docs/code-quality/ca0052.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0052
diff --git a/docs/code-quality/ca0053.md b/docs/code-quality/ca0053.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0053
diff --git a/docs/code-quality/ca0054.md b/docs/code-quality/ca0054.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0054
diff --git a/docs/code-quality/ca0055.md b/docs/code-quality/ca0055.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0055
diff --git a/docs/code-quality/ca0056.md b/docs/code-quality/ca0056.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0056
diff --git a/docs/code-quality/ca0057.md b/docs/code-quality/ca0057.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0057
diff --git a/docs/code-quality/ca0058.md b/docs/code-quality/ca0058.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0058
diff --git a/docs/code-quality/ca0059.md b/docs/code-quality/ca0059.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0059
diff --git a/docs/code-quality/ca0060.md b/docs/code-quality/ca0060.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0060
diff --git a/docs/code-quality/ca0061.md b/docs/code-quality/ca0061.md
@@ -9,7 +9,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0061
diff --git a/docs/code-quality/ca0062.md b/docs/code-quality/ca0062.md
@@ -9,7 +9,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0062
diff --git a/docs/code-quality/ca0063.md b/docs/code-quality/ca0063.md
@@ -9,7 +9,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0063
diff --git a/docs/code-quality/ca0064.md b/docs/code-quality/ca0064.md
@@ -9,7 +9,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0064
diff --git a/docs/code-quality/ca0065.md b/docs/code-quality/ca0065.md
@@ -7,7 +7,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0065
diff --git a/docs/code-quality/ca0066.md b/docs/code-quality/ca0066.md
@@ -7,7 +7,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0066
diff --git a/docs/code-quality/ca0067.md b/docs/code-quality/ca0067.md
@@ -9,7 +9,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0067
diff --git a/docs/code-quality/ca0068.md b/docs/code-quality/ca0068.md
@@ -9,7 +9,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0068
diff --git a/docs/code-quality/ca0069.md b/docs/code-quality/ca0069.md
@@ -7,7 +7,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0069
diff --git a/docs/code-quality/ca0070.md b/docs/code-quality/ca0070.md
@@ -9,7 +9,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0070
diff --git a/docs/code-quality/ca0501.md b/docs/code-quality/ca0501.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0501
diff --git a/docs/code-quality/ca0502.md b/docs/code-quality/ca0502.md
@@ -11,7 +11,6 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: code-analysis
-
 ---
 
 # CA0502
diff --git a/docs/debugger/debug-with-copilot.md b/docs/debugger/debug-with-copilot.md
@@ -15,6 +15,7 @@ author: mikejo5000
 ms.author: mikejo
 manager: mijacobs
 ms.subservice: ai-tools
+ms.collection: ce-skilling-ai-copilot
 monikerRange: '>= vs-2022'
 ---
 
diff --git a/docs/designers/walkthrough-windows-forms-designer.md b/docs/designers/walkthrough-windows-forms-designer.md
@@ -1,7 +1,7 @@
 ---
 title: Windows Forms Designer tutorial
 description: 'Use Windows Forms Designer to build applications and arrange controls, set margins and padding, adjust layout, size, and display, and set property values.'
-ms.date: 07/10/2023
+ms.date: 07/15/2024
 ms.topic: tutorial
 helpviewer_keywords:
 - Windows Forms Designer, get started
@@ -46,14 +46,14 @@ The Windows Forms Designer shows the designer surface for the DemoCalculator con
 
 The DemoCalculator control contains several Windows Forms controls. In this procedure, you'll arrange the controls by using the Windows Forms Designer.
 
-1. In the Windows Forms Designer, change the DemoCalculator control to a larger size by selecting the sizing handle in the lower-right corner and dragging it down and to the right. In the lower-right corner of Visual Studio, find the size and location information for controls. Set the size of the control to width 500 and height 400 by watching the size information as you resize the control.
+1. In the Windows Forms Designer, change the DemoCalculator control to a larger size by selecting the sizing handle in the lower-right corner and dragging it to resize. In the lower-right corner of Visual Studio, find the size and location information for controls. Set the size of the control to width 1000 and height 800 by watching the size information as you resize the control. You can also scroll down to the bottom of the **Properties** window, which is usually docked the lower right corner, and manually enter the values in the **Size** property.
 
 1. In **Toolbox**, select the **Containers** node to open it. Select the **SplitContainer** control and drag it onto the designer surface.
 
    The `SplitContainer` is placed on the DemoCalculator control's designer surface.
 
     > [!TIP]
-    > The `SplitContainer` control sizes itself to the fit the size of the DemoCalculator control. Look at the **Properties** window to see the property settings for the `SplitContainer` control. Find the <xref:System.Windows.Forms.SplitContainer.Dock%2A> property. Its value is [DockStyle.Fill](xref:System.Windows.Forms.DockStyle.Fill), which means the `SplitContainer` control will always size itself to the boundaries of the DemoCalculator control. Resize the DemoCalculator control to verify this behavior.
+    > The `SplitContainer` control sizes itself to fit the size of the DemoCalculator control. Look at the **Properties** window to see the property settings for the `SplitContainer` control. Find the <xref:System.Windows.Forms.SplitContainer.Dock%2A> property. Its value is [DockStyle.Fill](xref:System.Windows.Forms.DockStyle.Fill), which means the `SplitContainer` control will always size itself to the boundaries of the DemoCalculator control. Resize the DemoCalculator control to verify this behavior.
 
 1. In the **Properties** window, change the value of the <xref:System.Windows.Forms.SplitContainer.Dock%2A> property to `None`.
 
@@ -152,11 +152,11 @@ Now that the layout of the control is set up, you can populate the DemoCalculato
 
 When your control or form is populated with several controls, you may find it easier to navigate your layout with the Document Outline window.
 
-1. On the menu bar, choose **View** > **Other Windows** > **Document Outline**.
+1. On the menu bar, choose **View** > **Other Windows** > **Document Outline**. Or, on the keyboard, press **Ctrl**+**Alt**+**T**.
 
    The Document Outline window shows a tree view of the DemoCalculator control and its constituent controls. Container controls like the `SplitContainer` show their child controls as subnodes in the tree. You can also rename controls in place by using the Document Outline window.
 
-1. In the **Document Outline** window, right-click **button1**, and then select **Rename**. Change its name to sevenButton.
+1. In the **Document Outline** window, right-click **button1**, and then select **Rename** (keyboard: **F2**). Change its name to sevenButton.
 
 1. Using the **Document Outline** window, rename the `Button` controls from the designer-generated name to the production name according to the following list:
 
@@ -250,6 +250,8 @@ The buttons on the DemoCalculator control have event handlers that can be used t
 
    The Code Editor opens to the event handlers generated by the designer.
 
+Since this tutorial is focused on the designer, we omit the implementation details of the calculator functionality.
+
 ## Test the control
 
 Because the DemoCalculator control inherits from the <xref:System.Windows.Forms.UserControl> class, you can test its behavior with the **UserControl Test Container**. For more information, see [How to: Test the run-time behavior of a UserControl](/dotnet/framework/winforms/controls/how-to-test-the-run-time-behavior-of-a-usercontrol).
@@ -268,15 +270,15 @@ The DemoCalculator control can be used in other composite controls or on a form.
 
 The first step is to create the application project. You'll use this project to build the application that shows your custom control.
 
-1. Create a new **Windows Forms Application** project and name it **DemoCalculatorTest**.
+1. Add a new **Windows Forms App (.NET Framework)** project to the existing solution and name it **DemoCalculatorTest**.
 
-1. In **Solution Explorer**, right-click the **DemoCalculatorTest** project, and then select **Add** > **Project Reference** to open the **Reference Manager** dialog box.
+1. In **Solution Explorer**, right-click the **DemoCalculatorTest** project, and then select **Add** > **Reference** to open the **Reference Manager** dialog box.
 
 1. Go to the **Projects** tab, and then select the DemoCalculatorLib project to add the reference to the test project.
 
 1. In **Solution Explorer**, right-click **DemoCalculatorTest**, and then select **Set as StartUp Project**.
 
-1. In the Windows Forms Designer, increase the size of the form to about **700 x 500**.
+1. In the Windows Forms Designer, increase the size of the form to about **1400 x 1000**.
 
 ### Use the control in the form's layout
 
diff --git a/docs/ide/ai-assisted-development-visual-studio.md b/docs/ide/ai-assisted-development-visual-studio.md
@@ -7,6 +7,7 @@ author: anandmeg
 ms.author: meghaanand
 ms.manager: mijacobs
 ms.subservice: ai-tools
+ms.collection: ce-skilling-ai-copilot
 monikerRange: vs-2022
 ---
 # AI-assisted development in Visual Studio
diff --git a/docs/ide/copilot-chat-context.md b/docs/ide/copilot-chat-context.md
@@ -7,6 +7,7 @@ author: anandmeg
 ms.author: meghaanand
 ms.manager: mijacobs
 ms.subservice: ai-tools
+ms.collection: ce-skilling-ai-copilot 
 helpviewer_keywords: 
   - copilot chat context
   - context, copilot chat
diff --git a/docs/ide/deploy-copilot-to-enterprise.md b/docs/ide/deploy-copilot-to-enterprise.md
@@ -1,33 +1,34 @@
 ---
 title: Deploy GitHub Copilot within your enterprise
 description: Configure and deploy GitHub Copilot programmatically to existing Visual Studio instances on a client's machine within an enterprise.
-ms.date: 1/11/2024
+ms.date: 7/15/2024
 ms.topic: conceptual
 author: anandmeg
 ms.author: meghaanand
 ms.manager: mijacobs
 ms.subservice: ai-tools
+ms.collection: ce-skilling-ai-copilot
 monikerRange: vs-2022
 ---
 # Deploy GitHub Copilot to existing Visual Studio instances
 
-For administrators of Visual Studio 2022 version 17.8 or above, you can deploy GitHub Copilot onto client workstations programmatically with an installation script, just like you deploy other [Visual Studio components](../install/workload-and-component-ids.md). 
+Administrators of Visual Studio 2022 version 17.8 or above can deploy GitHub Copilot onto client workstations programmatically with an installation script, just like you deploy other [Visual Studio components](../install/workload-and-component-ids.md). 
 
-Note that this method does NOT install the GitHub Copilot chat extension.
+This method does NOT install the GitHub Copilot chat extension.
 
-## Pre-requisites
+## Prerequisites
 
 To get started, you need:
 
-- This section assumes that Visual Studio 2022 [version 17.8 or later](/visualstudio/releases/2022/release-history) is already installed on the client machines.  If it's not, refer to the guidance in the [Visual Studio Administrators Guide](https://aka.ms/vs/admin/guide) for how to deploy Visual Studio throughout your organization.
+- This section assumes that Visual Studio 2022 [version 17.8 or later](/visualstudio/releases/2022/release-history) is already installed on the client machines. If it's not, refer to the guidance in the [Visual Studio Administrators Guide](https://aka.ms/vs/admin/guide) for how to deploy Visual Studio throughout your organization.
 - A valid and active GitHub Copilot for Business subscription is required for the end user whose Visual Studio 2022 instance you're installing the GitHub Copilot component for. 
 [See: Managing access for GitHub Copilot for Business in your organization.](https://docs.github.com/en/copilot/managing-copilot-business/managing-access-for-copilot-business-in-your-organization)
 
 Options for deploying GitHub Copilot onto client machines depend on how Visual Studio is currently installed on these machines.
 
 ## Modify an existing installation to add the GitHub Copilot component
 
-Most of the time, users would've either acquired Visual Studio themselves, or run a development environment setup script on their machine.
+Most of the time, users would either acquire Visual Studio themselves, or run a development environment setup script on their machine.
 To add the GitHub Copilot component to an existing installation of Visual Studio, use the installer's `modify` command from either a command line or PowerShell window.
 
 ### Sample install instructions
@@ -46,14 +47,14 @@ foreach ($i in $installDir) {
 
 If you're using a layout to deploy Visual Studio across your organization, you first need to add the `Component.GitHub.Copilot` component to the layout.  Then, assuming the client is configured to [receive updates from the layout](../install/update-visual-studio.md#configure-source-location-of-updates), you can run a `modify` command as in the previous example to add it to the client.
 
-Refer to the [layout documentation](../install/create-a-network-installation-of-visual-studio.md#modify-the-contents-of-a-layout) for further information. 
+For more information, see the [layout documentation](../install/create-a-network-installation-of-visual-studio.md#modify-the-contents-of-a-layout). 
 
 ## End user action required
 
-Note that after installing the GitHub Copilot component to the client machines, the end user will need to take the following steps to enable GitHub Copilot:
+After installing the GitHub Copilot component to the client machines, the end user will need to take the following steps to enable GitHub Copilot:
 
 1. Log into the [GitHub web interface](https://github.com/settings/copilot) with the GitHub account associated with their Copilot subscription.
-1. Launch Visual Studio 2022 and [add their GitHub account to the Visual Studio keychain to activate access](work-with-github-accounts.md).
+1. Activate access by launching Visual Studio 2022 and [adding their GitHub account to the Visual Studio keychain](work-with-github-accounts.md).
 
 ## Related content
 
diff --git a/docs/ide/using-the-task-list.md b/docs/ide/using-the-task-list.md
@@ -1,7 +1,7 @@
 ---
 title: Use the Task List to track and use code comments
 description: Explore the Task List in Visual Studio and discover how the tool can help you track and use code comments more efficiently.
-ms.date: 06/22/2023
+ms.date: 07/10/2024
 ms.topic: how-to
 f1_keywords:
 - TaskListWindow
@@ -17,7 +17,7 @@ ms.subservice: general-ide
 ---
 # Use the Task List
 
-Use **Task List** to track code comments that use tokens such as `TODO` and `HACK`, or custom tokens, and to manage shortcuts that take you directly to a predefined location in code. Select an item in the list to go to its location in the source code.
+Use **Task List** to track code comments that use tokens such as `TODO` and `HACK`, or custom tokens, and to manage shortcuts that take you directly to a predefined location in code. Double-click an item in the list (or select an item and press **ENTER**) to go to its location in the source code.
 
 > [!NOTE]
 > This topic applies to Visual Studio on Windows. For Visual Studio for Mac, see [Task comments (Visual Studio for Mac)](/visualstudio/mac/task-comments).
@@ -30,9 +30,9 @@ To open **Task List**, select **View** > **Task List**, or from the keyboard pre
 
 ![Screenshot of the Task List window.](media/task-list-window.png)
 
-To change the sort order of the list, select the header of any column. To further refine your search results, press **Shift** and select a second column header. Alternatively, on the shortcut menu, choose **Sort by**, and then choose a header. To further refine your search results, press **Shift** and choose a second header.
+To change the sort order of the list, select the header of any column. To further refine your search results, press **Shift** and select a second column header. To further refine your search results, press **Shift** and choose a second header.
 
-To show or hide columns, on the shortcut menu, choose **Show Columns**. Select the columns that you want to show or hide.
+To show or hide columns, on the shortcut (right-click) menu, choose **Show Columns**. Select the columns that you want to show or hide.
 
 To change the order of the columns, drag any column header to the location that you want.
 
diff --git a/docs/ide/visual-studio-github-copilot-admin.md b/docs/ide/visual-studio-github-copilot-admin.md
@@ -7,6 +7,7 @@ author: anandmeg
 ms.author: meghaanand
 ms.manager: mijacobs
 ms.subservice: ai-tools
+ms.collection: ce-skilling-ai-copilot
 monikerRange: vs-2022
 ---
 
diff --git a/docs/ide/visual-studio-github-copilot-chat.md b/docs/ide/visual-studio-github-copilot-chat.md
@@ -7,6 +7,7 @@ author: anandmeg
 ms.author: meghaanand
 ms.manager: mijacobs
 ms.subservice: ai-tools
+ms.collection: ce-skilling-ai-copilot
 monikerRange: '>= vs-2022'
 ---
 # What is the GitHub Copilot Chat extension for Visual Studio?
diff --git a/docs/ide/visual-studio-github-copilot-extension.md b/docs/ide/visual-studio-github-copilot-extension.md
@@ -7,6 +7,7 @@ author: anandmeg
 ms.author: meghaanand
 ms.manager: mijacobs
 ms.subservice: ai-tools
+ms.collection: ce-skilling-ai-copilot
 monikerRange: '>= vs-2022'
 content_well_notification: 
   - AI-contribution
diff --git a/docs/ide/visual-studio-github-copilot-install-and-states.md b/docs/ide/visual-studio-github-copilot-install-and-states.md
@@ -7,6 +7,7 @@ author: anandmeg
 ms.author: meghaanand
 ms.manager: mijacobs
 ms.subservice: ai-tools
+ms.collection: ce-skilling-ai-copilot 
 monikerRange: '>= vs-2022'
 ---
 # Install GitHub Copilot in Visual Studio
diff --git a/docs/ide/visual-studio-github-copilot-troubleshoot.md b/docs/ide/visual-studio-github-copilot-troubleshoot.md
