Merge pull request #10329 from MicrosoftDocs/main

8/22 PM Publishing

Author: v-alje

docs/debugger/getting-started-with-the-debugger-cpp.md

@@ -2,7 +2,7 @@
 title: "Tutorial: Debug C++ code"
 description: Learn features of the Visual Studio debugger and how to start the debugger, step through code, and inspect data in a C++ application.
 ms.custom: "debug-experiment,  vs-acquisition, get-started"
-ms.date: 02/04/2020
+ms.date: 08/18/2022
 ms.technology: vs-ide-debug
 ms.topic: tutorial
 dev_langs:
@@ -53,9 +53,6 @@ If you need to install the workload but already have Visual Studio, go to **Tool
 
 First, you'll create a C++ console application project. The project type comes with all the template files you'll need, before you've even added anything!
 
-
-::: moniker range=">=vs-2019"
-
 1. Open Visual Studio.
 
    If the start window is not open, choose **File** > **Start Window**.
@@ -66,7 +63,12 @@ First, you'll create a C++ console application project. The project type comes w
 
    After you apply the language and platform filters, choose the **Console App** template, and then choose **Next**.
 
-   ![Choose the C++ template for the Console App](../debugger/media/vs-2019/get-started-create-console-project-cpp.png)
+   ::: moniker range=">= vs-2022"
+   ![Screenshot of choosing the C++ template for the Console App.](../debugger/media/vs-2022/get-started-create-console-project-cpp.png)
+   ::: moniker-end
+   ::: moniker range="vs-2019"
+   ![Screenshot of choosing the C++ template for the Console App.](../debugger/media/vs-2019/get-started-create-console-project-cpp.png)
+   ::: moniker-end
 
    > [!NOTE]
    > If you do not see the **Console App** template, you can install it from the **Create a new project** window. In the **Not finding what you're looking for?** message, choose the **Install more tools and features** link. Then, in the Visual Studio Installer, choose the **Desktop development with C++** workload.
@@ -75,8 +77,6 @@ First, you'll create a C++ console application project. The project type comes w
 
    Visual Studio opens your new project.
 
-::: moniker-end
-
 ## Create the application
 
 1. In *get-started-debugging.cpp*, replace all of the default code with the following code instead:
@@ -146,7 +146,7 @@ First, you'll create a C++ console application project. The project type comes w
 
 2. Press **F5** or the **Start Debugging** button ![Start Debugging](../debugger/media/dbg-tour-start-debugging.png "Start Debugging"), the app starts, and the debugger runs to the line of code where you set the breakpoint.
 
-    ![Set and hit a breakpoint](../debugger/media/get-started-set-breakpoint-cpp.png)
+    ![Screenshot of setting and hitting a breakpoint.](../debugger/media/get-started-set-breakpoint-cpp.png)
 
     The yellow arrow represents the statement on which the debugger paused, which also suspends app execution at the same point (this statement has not yet executed).
 
@@ -168,7 +168,7 @@ Mostly, we use the keyboard shortcuts here, because it's a good way to get fast
 
      The yellow pointer advances into the `SendMessage` method.
 
-     ![Use F11 to Step Into code](../debugger/media/get-started-f11-cpp.png "F10 Step Into")
+     ![Screenshot of  using F11 to Step Into code.](../debugger/media/get-started-f11-cpp.png "F10 Step Into")
 
      F11 is the **Step Into** command and advances the app execution one statement at a time. F11 is a good way to examine the execution flow in the most detail. (To move faster through code, we show you some other options also.) By default, the debugger skips over non-user code (if you want more details, see [Just My Code](../debugger/just-my-code.md)).
 
@@ -184,7 +184,7 @@ Mostly, we use the keyboard shortcuts here, because it's a good way to get fast
 
 1. While paused at the method call, press **F10** (or choose **Debug > Step Over**) once.
 
-     ![Use F10 to Step Over code](../debugger/media/get-started-step-over-cpp.png "F10 Step Over")
+     ![Screenshot of using F10 to Step Over code.](../debugger/media/get-started-step-over-cpp.png "F10 Step Over")
 
      Notice this time that the debugger does not step into the `SendMessage` method. **F10** advances the debugger without stepping into functions or methods in your app code (the code still executes). By pressing **F10** on the `SendMessage` method call (instead of **F11**), we skipped over the implementation code for `SendMessage` (which maybe we're not interested in right now). For more information on different ways to move through your code, see [Navigate code in the debugger](../debugger/navigating-through-code-with-the-debugger.md).
 
@@ -194,7 +194,7 @@ Mostly, we use the keyboard shortcuts here, because it's a good way to get fast
 
 1. In the code editor, scroll down and hover over the `std::wcout` function in the `SendMessage` method until the green **Run to Click** button ![Run to Click](../debugger/media/dbg-tour-run-to-click.png "RunToClick") appears on the left. The tooltip for the button shows "Run execution to here".
 
-     ![Use the Run to Click feature](../debugger/media/get-started-run-to-click-cpp.png "Run to Click")
+     ![Screenshot of using the Run to Click feature.](../debugger/media/get-started-run-to-click-cpp.png "Run to Click")
 
    > [!NOTE]
    > The **Run to Click** button is new in [!include[vs_dev15](../misc/includes/vs_dev15_md.md)]. (If you don't see the green arrow button, use **F11** in this example instead to advance the debugger to the right place.)
@@ -225,7 +225,7 @@ Features that allow you to inspect variables are one of the most useful features
 
 1. Press **F5** (or **Debug** > **Continue**) a few times to iterate several times through the `for` loop, pausing again at the breakpoint, and hovering over the `name` variable each time to check its value.
 
-     ![View a data tip](../debugger/media/get-started-data-tip-cpp.png "View a Data Tip")
+     ![Screenshot of viewing a data tip.](../debugger/media/get-started-data-tip-cpp.png "View a Data Tip")
 
      The value of the variable changes with each iteration of the `for` loop, showing values of `f`, then `fr`, then `fre`, and so on.
 
@@ -243,9 +243,14 @@ Features that allow you to inspect variables are one of the most useful features
 
 1. Expand the `letters` variable to show the elements that it contains.
 
-     ![Inspect variables in the Locals Window](../debugger/media/get-started-locals-window-cpp.png "Locals Window")
+   ::: moniker range=">= vs-2022"
+   ![Screenshot of inspecting variables in the Locals Window.](../debugger/media/vs-2022/get-started-locals-window-cpp.png "Locals Window")
+   ::: moniker-end
+   ::: moniker range="vs-2019"
+   ![Screenshot of inspecting variables in the Locals Window.](../debugger/media/get-started-locals-window-cpp.png "Locals Window")
+   ::: moniker-end
 
-    The **Locals** window shows you the variables that are in the current [scope](https://www.wikipedia.org/wiki/Scope_(computer_science)), that is, the current execution context.
+   The **Locals** window shows you the variables that are in the current [scope](https://www.wikipedia.org/wiki/Scope_(computer_science)), that is, the current execution context.
 
 ## Set a watch
 
@@ -263,7 +268,12 @@ Features that allow you to inspect variables are one of the most useful features
 
 2. Click **F11** a few times until you see the debugger pause in the `SendMessage` method. Look at the **Call Stack** window.
 
-    ![Examine the call stack](../debugger/media/get-started-call-stack-cpp.png "ExamineCallStack")
+    ::: moniker range=">= vs-2022"
+    ![Screenshot of examining the call stack.](../debugger/media/vs-2022/get-started-call-stack-cpp.png "ExamineCallStack")
+    ::: moniker-end
+    ::: moniker range="vs-2019"
+    ![Screenshot of examining the call stack.](../debugger/media/get-started-call-stack-cpp.png "ExamineCallStack")
+    ::: moniker-end
 
     The **Call Stack** window shows the order in which methods and functions are getting called. The top line shows the current function (the `SendMessage` method in this app). The second line shows that `SendMessage` was called from the `main` method, and so on.
 

docs/debugger/media/vs-2022/get-started-call-stack-cpp.png

@@ -2,7 +2,7 @@
 title: "Remote Debug a C# or VB project | Microsoft Docs"
 description: Learn how to debug a Visual Studio C# or Visual Basic application from a remote computer by following these step-by-step instructions.
 ms.custom: ['remotedebugging"=']
-ms.date: "02/23/2022"
+ms.date: "08/22/2022"
 ms.topic: "conceptual"
 dev_langs:
   - "C++"
@@ -64,7 +64,7 @@ The debugger cannot deploy Visual C# or Visual Basic desktop applications to a r
 4. On the **Properties** page, choose the **Debug** tab.
 
     ::: moniker range="vs-2022"
-    For C# projects targeting .NET Core or .NET 5 and later, starting in Visual Studio 2022, choose the **Debug launch profiles UI** from the **Debug** tab to configure settings for remote debugging.
+    For C# projects targeting .NET Core or .NET 5+, starting in Visual Studio 2022, choose the **Debug launch profiles UI** from the **Debug** tab to configure settings for remote debugging.
 
     ![Screenshot of the Debug launch profile UI in the Visual Studio Project Properties for C# and .NET.](../debugger/media/vs-2022/remote-debugger-csharp.png)
 
@@ -85,7 +85,6 @@ The debugger cannot deploy Visual C# or Visual Basic desktop applications to a r
     **MJO-DL:4024** on Visual Studio 2019
     ::: moniker-end
 
-
 7. Make sure that **Enable native code debugging** is not selected.
 
 8. Build the project.

docs/debugger/media/vs-2022/get-started-create-console-project-cpp.png

@@ -4,7 +4,7 @@ author: evanwindom
 ms.author: amast
 manager: shve
 ms.assetid: e49242bc-e9f2-49e8-8caa-f574d508aba6
-ms.date: 08/15/2022
+ms.date: 08/22/2022
 ms.topic: how-to
 description:  Learn how admins can delete subscription assignments in the Visual Studio Subscriptions Administration Portal
 ---
@@ -69,6 +69,7 @@ admin on the agreement through which the subscriptions were purchased.
    > [!div class="mx-imgBorder"]
    > ![Duplicates highlighted](_img/delete-license/duplicates-highlighted.png "Screenshot of bulk edit template showing the columns for all users and the users to be deleted selected.  The user names to be deleted are highlighted.")
 
+0. Select a cell in the spreadsheet.  This will de-select the two columns.  
 0. On the **Data** tab, choose **Filter**.
 0. Select the filter drop-down in column "B", choose **Sort by color**, and select the color that was applied to the duplicate cells.  You should now see only the users that will be deleted.  
 0. In the **Reference** column for each user, enter a word or phrase that you can use to filter on to find only the users you want to delete.  Use the same term for all of the users.  In our example, we'll use "DELETE USER".  You can use the "fill down" feature in Excel to replicate the phrase for all of the users.  Your template show now look like this:
@@ -79,12 +80,12 @@ admin on the agreement through which the subscriptions were purchased.
 0. Switch back to the admin portal.  The **Edit multiple subscribers** dialog should still be open.  (If it's not, just select the **Bulk edit** option again.) 
 0. Select the **Browse** button, select the file you just saved, and select **Open**.  The name of your file will now be displayed in the dialog.
 0. Select **OK**.
-0. You should now see your subscriber list.  The subscribers you want to delete should have the phrase you defined listed in the **Reference** column.
+0. You should now see your subscriber list.  The subscribers you want to delete should have the phrase you defined listed in the **Reference** column. If it's not visible and you want to display it, select the **Edit columns** menu option and add the column.
    > [!div class="mx-imgBorder"]
    > ![List Showing Reference](_img/delete-license/reference-list.png "Screenshot of subscriber list in the admin portal showing the addition of the reference term marking users to be deleted.")
 
-0. In the **Filter by name, email or reference** field, enter the word or phrase you used to mark the users to be deleted.  
-0. You should now see only the users you need to delete.  You can select one users, then use CTRL+A to select them all, and choose **Delete**.
+0. In the **Filter by name, email or reference** field, enter the word or phrase you used to mark the users to be deleted. The filter will be applied even if the **Reference** column is not displayed.
+0. You should now see only the users you need to delete.  You can select one user, then use CTRL+A to select them all, and choose **Delete**.
 0. Clear the filter field to display your updated subscriber list.