Merge pull request #6258 from MicrosoftDocs/master637448833872568919

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: ghogen

docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md

@@ -1,5 +1,6 @@
 ---
 title: "Remote debug ASP.NET on an IIS computer"
+description: Learn how to set up and configure a Visual Studio ASP.NET MVC 4.5.2 application, deploy it to IIS, and attach the remote debugger from Visual Studio. 
 ms.custom: ['remotedebugging', 'seodec18']
 ms.date: 05/06/2020
 ms.topic: "conceptual"
@@ -83,7 +84,7 @@ If you want more detailed information to install ASP.NET on IIS, see [IIS 8.0 Us
 
 1. Use the Web Platform Installer (WebPI) to install ASP.NET 4.5 (from the Server node in Windows Server 2012 R2, choose **Get New Web Platform Components** and then search for ASP.NET)
 
-    ![RemoteDBG_IIS_AspNet_45](../debugger/media/remotedbg_iis_aspnet_45.png "RemoteDBG_IIS_AspNet_45")
+    ![Screenshot of the Web Platform Installer 5.0 showing the search results for asp.net with the web platform component IIS: ASP.NET 4.5 circled in red.](../debugger/media/remotedbg_iis_aspnet_45.png)
 
     > [!NOTE]
     > If you are using Windows Server 2008 R2, install ASP.NET 4 instead using this command:

docs/debugger/remote-debugging-azure.md

@@ -1,5 +1,6 @@
 ---
 title: "Remote Debug ASP.NET Core on IIS and Azure | Microsoft Docs"
+description: Learn how to set up and configure a Visual Studio ASP.NET Core app, deploy it to IIS using Azure, and attach the remote debugger from Visual Studio. 
 ms.custom: "remotedebugging"
 ms.date: 05/06/2020
 ms.topic: "conceptual"
@@ -24,13 +25,13 @@ The recommended way to remote debug on Azure depends on your scenario:
 
     In this scenario, you must deploy your app from Visual Studio to Azure but you do not need to manually install or configure IIS or the remote debugger (these components are represented with dotted lines), as shown in the following illustration.
 
-    ![Remote debugger components](../debugger/media/remote-debugger-azure-app-service.png "Remote_debugger_components")
+    ![Diagram showing the relationship between Visual Studio, Azure App Service, and an ASP.NET app. IIS and the Remote Debugger are represented with dotted lines.](../debugger/media/remote-debugger-azure-app-service.png)
 
 * To debug IIS on an Azure VM, follow steps in this topic (see the section [Remote Debug on an Azure VM](#remote_debug_azure_vm)). This allows you to use a customized configuration of IIS, but the setup and deployment steps are more complicated.
 
     For an Azure VM, you must deploy your app from Visual Studio to Azure and you also need to manually install the IIS role and the remote debugger, as shown in the following illustration.
 
-    ![Remote debugger components](../debugger/media/remote-debugger-azure-vm.png "Remote_debugger_components")
+    ![Diagram showing the relationship between Visual Studio, an Azure VM, and an ASP.NET app. IIS and the Remote Debugger are represented with solid lines.](../debugger/media/remote-debugger-azure-vm.png)
 
 * To debug ASP.NET Core on Azure Service Fabric, see [Debug a remote Service Fabric application](/azure/service-fabric/service-fabric-debugging-your-application#debug-a-remote-service-fabric-application).
 
@@ -202,7 +203,7 @@ If you are importing publish settings, you can skip this section.
 
 ### (Optional) Publish and Deploy the app by publishing to a local folder from Visual Studio
 
-If you're not using Web Deploy, you must publish and deploy the app using the file system or other tools. You can start by creating a package using the file system, and then either deploy the package manually or use other tools like PowerShell, RoboCopy, or XCopy. In this section, we assume you are manually copying the package if you are not using Web Deploy.
+If you're not using Web Deploy, you must publish and deploy the app using the file system or other tools. You can start by creating a package using the file system, and then either deploy the package manually or use other tools like PowerShell, Robocopy, or XCopy. In this section, we assume you are manually copying the package if you are not using Web Deploy.
 
 [!INCLUDE [remote-debugger-deploy-app-local](../debugger/includes/remote-debugger-deploy-app-local.md)]
 

docs/debugger/remote-debugging-cpp.md

@@ -1,5 +1,6 @@
 ---
 title: "Remote Debug a C++ Project | Microsoft Docs"
+description: Learn how to debug a Visual Studio C++ application from a remote computer by following these step-by-step instructions.
 ms.custom: "remotedebugging"
 ms.date: "08/14/2018"
 ms.topic: "conceptual"
@@ -57,7 +58,7 @@ The remote debugger is supported on Windows 7 and newer (not phone) and versions
 
 4. Set the **Debugger to launch** to **Remote Windows Debugger**.
 
-    ![RemoteDebuggingCPlus](../debugger/media/remotedebuggingcplus.png "RemoteDebuggingCPlus")
+    ![Screenshot of the Debugging tab in the Visual Studio Solution Explorer Properties. The Debugger to launch property is set to Remote Windows Debugger.](../debugger/media/remotedebuggingcplus.png)
 
 5. Make the following changes to the properties:
 
@@ -77,7 +78,7 @@ The remote debugger is supported on Windows 7 and newer (not phone) and versions
 
 7. For the **Debug** configuration, select the **Deploy** check box.
 
-    ![RemoteDebugCplusDeploy](../debugger/media/remotedebugcplusdeploy.png "RemoteDebugCplusDeploy")
+    ![Screenshot of the Configuration Manager in the Visual Studio Solution Explorer. The Debug configuration is selected, and Deploy is checked.](../debugger/media/remotedebugcplusdeploy.png)
 
 8. Start debugging (**Debug > Start Debugging**, or **F5**).
 

docs/debugger/remote-debugging-csharp.md

@@ -1,5 +1,6 @@
 ---
 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"=', 'seodec18']
 ms.date: "08/14/2018"
 ms.topic: "conceptual"
@@ -59,7 +60,7 @@ The debugger cannot deploy Visual C# or Visual Basic desktop applications to a r
 
 4. On the **Properties** page, choose the **Debug** tab.
 
-    ![RemoteDebuggerCSharp](../debugger/media/remotedebuggercsharp.png "RemoteDebuggerCSharp")
+    ![Screenshot of the Debug tab in the Visual Studio Solution Explorer Properties. The Use remote machine property is set to 'MJO-DL:4022'.](../debugger/media/remotedebuggercsharp.png)
 
 5. Make sure the **Working directory** text box is empty.
 
@@ -84,11 +85,11 @@ The debugger cannot deploy Visual C# or Visual Basic desktop applications to a r
     > [!CAUTION]
     > Do not make changes to the code or rebuild (or you must repeat this step). The executable you copied to the remote machine must exactly match your local source and symbols.
 
-    You can copy the project manually, use Xcopy, Robocopy, Powershell, or other options.
+    You can copy the project manually, use XCopy, Robocopy, Powershell, or other options.
 
 11. Make sure the remote debugger is running on the target machine (If it's not, search for **Remote Debugger** in the **Start** menu). The remote debugger window looks like this.
 
-     ![RemoteDebuggerWindow](../debugger/media/remotedebuggerwindow.png "RemoteDebuggerWindow")
+     ![Screenshot of the Visual Studio 2017 Remote Debugger window. One action is listed that indicates the debugger is running on the target machine.](../debugger/media/remotedebuggerwindow.png)
 
 12. In Visual Studio, start debugging (**Debug > Start Debugging**, or **F5**).
 

docs/debugger/walkthrough-using-intellitrace.md

@@ -1,5 +1,6 @@
 ---
 title: "View events with IntelliTrace | Microsoft Docs"
+description: Learn how to use IntelliTrace in Visual Studio Enterprise to collect data about specific events, categories of events, and individual function calls.
 ms.date: "11/04/2016"
 ms.topic: "conceptual"
 ms.assetid: e1c9c91a-0009-4c4e-9b4f-c9ab3a6022a7
@@ -58,21 +59,21 @@ You can try debugging with just IntelliTrace events. IntelliTrace events are deb
 
     The following screenshot is from Visual Studio 2015 Update 1.
 
-    ![IntelliTrace-Update1](../debugger/media/intellitrace-update1.png "IntelliTrace-Update1")
+    ![Screenshot of the Visual Studio code window. Execution is stopped at a breakpoint and the Events tab in the Diagnostic Tools window lists events.](../debugger/media/intellitrace-update1.png)
 
 3. Select the event to expand its details.
 
     The following screenshot is from Visual Studio 2015 Update 1.
 
-    ![IntelliTraceUpdate1-SingleEvent](../debugger/media/intellitraceupdate1-singleevent.png "IntelliTraceUpdate1-SingleEvent")
+    ![Screenshot of the Events tab in the Visual Studio Diagnostic Tools window. An event is selected and expanded to show it's details.](../debugger/media/intellitraceupdate1-singleevent.png)
 
     You can choose the pathname link to open the file. If the full pathname is not available, the **Open File** dialog box appears.
 
     Click **Activate Historical Debugging**, which sets the debugger's context to the time when the selected event was collected, showing historical data in the **Call Stack**, **Locals** and the other participating debugger windows. If source code is available, Visual Studio moves the pointer to the corresponding code in the source window so you can examine it.
 
     The following screenshot is from Visual Studio 2015 Update 1.
 
-    ![HistoricalDebugging-Update1](../debugger/media/historicaldebugging-update1.png "HistoricalDebugging-Update1")
+    ![Screenshot of the Visual Studio code window. Execution is stopped at a breakpoint, an event is selected, and the corresponding code line is highlighted.](../debugger/media/historicaldebugging-update1.png)
 
 4. If you didn't find the bug, try examining other events leading up to the bug. You can also have IntelliTrace record call information so you can step through function calls.
 

docs/deployment/quickstart-deploy-to-azure.md

@@ -47,11 +47,11 @@ This article describes how to use the **Publish** tool for one-time deployment.
 
 1. In the **Create Azure App Service (Windows)** dialog, the **App Name**, **Resource Group**, and **App Service Plan** entry fields are populated. You can keep these names or change them. When ready, select **Create**.
 
-    ![Choose Azure App Service](../deployment/media/quickstart-publish-windows-create-new-dialog.png)
+    ![Screenshot of the Create Azure App Service (Windows) dialog with the Name, Subscription, Resource Group, and Hosting Plan fields populated.](../deployment/media/quickstart-publish-windows-create-new-dialog.png)
 
 1. In the **Publish** dialog, the newly created instance has been automatically selected. When ready, select **Finish**.
 
-    ![Choose Azure App Service](../deployment/media/quickstart-publish-windows-select-instance.png)
+    ![Screenshot of the Publish window accessed from Visual Studio Solution Explorer. Azure is selected as the publishing target.](../deployment/media/quickstart-publish-windows-select-instance.png)
 
 1. Select **Publish**. Visual Studio deploys the app to your Azure App Service, and the web app loads in your browser. The project properties **Publish** pane shows the site URL and other details.
 

docs/deployment/quickstart-deploy-to-linux.md

@@ -46,11 +46,11 @@ This article describes how to use the **Publish** tool for one-time deployment.
 
 1. In the **Create Azure App Service (Linux)** dialog, the **App Name**, **Resource Group**, and **App Service Plan** entry fields are populated. You can keep these names or change them. When ready, select **Create**.
 
-    ![Choose Azure App Service](../deployment/media/quickstart-publish-linux-create-new-dialog.png)
+    ![Screenshot of the Create Azure App Service (Linux) dialog with the Name, Subscription, Resource Group, and Hosting Plan fields populated.](../deployment/media/quickstart-publish-linux-create-new-dialog.png)
 
 1. In the **Publish** dialog, the newly created instance has been automatically selected. When ready, click **Finish**.
 
-    ![Choose Azure App Service](../deployment/media/quickstart-publish-linux-select-instance.png)
+    ![Screenshot of the Publish dialog with the newly created MyASpCoreWebAppOnAzure service selected as the App Service for publishing.](../deployment/media/quickstart-publish-linux-select-instance.png)
 
 1. Select **Publish**. Visual Studio deploys the app to your Azure App Service, and the web app loads in your browser. The project properties **Publish** pane shows the site URL and other details.
 

docs/get-started/csharp/tutorial-debugger.md

@@ -1,6 +1,6 @@
 ---
 title: "Tutorial: Debug C# code"
-description: "Learn how to start the Visual Studio debugger, step through code, and inspect data."
+description: Learn features of the Visual Studio debugger and how to start the debugger, step through code, and inspect data.
 ms.custom: "debug-experiment, seodec18, get-started"
 ms.date: 04/23/2020
 ms.technology: "vs-ide-debug"
@@ -181,7 +181,7 @@ Mostly, we use the keyboard shortcuts here, because it's a good way to get fast
 
 1. Expand the `letters` variable to see its properties, which include all the elements that the variable contains.
 
-     ![View a data tip](../csharp/media/get-started-view-data-tip.png "View a Data Tip")
+     ![Screenshot of the Visual Studio Debugger with the 'name+= letters[I]' statement highlighted and a drop down list showing the elements in the letters array.](../csharp/media/get-started-view-data-tip.png)
 
 1. Next, hover over the `name` variable, and you see its current value, an empty string.
 
@@ -191,7 +191,7 @@ Mostly, we use the keyboard shortcuts here, because it's a good way to get fast
 
 1. Press **F10** (or **Debug** > **Step Over**) 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](../csharp/media/get-started-data-tip.gif "View a Data Tip")
+     ![An animated screenshot of the Visual Studio Debugger showing the effect of pressing F10 to "Step Over" and iterate through a loop during debugging.](../csharp/media/get-started-data-tip.gif)
 
      The value of the variable changes with each iteration of the `for` loop, showing values of `f`, then `fr`, then `fre`, and so on. To advance the debugger through the loop faster in this scenario, you can press **F5** (or choose **Debug** > **Continue**) instead, which advances you to the breakpoint instead of the next statement.
 

docs/javascript/debug-nodejs.md

@@ -24,7 +24,7 @@ You can debug JavaScript and TypeScript code using Visual Studio. You can set an
 
 1. With your project open in Visual Studio, open a server-side JavaScript file (such as *server.js*), click in the gutter to the left gutter to set a breakpoint:
 
-    ![Set a breakpoint](../javascript/media/tutorial-nodejs-react-set-breakpoint.png)
+    ![Screenshot of the Visual Studio code window showing JavaScript code. A red dot in the left gutter indicates that a breakpoint is set.](../javascript/media/tutorial-nodejs-react-set-breakpoint.png)
 
     Breakpoints are the most basic and essential feature of reliable debugging. A breakpoint indicates where Visual Studio should suspend your running code so you can take a look at the values of variables, or the behavior of memory, or whether or not a branch of code is getting run.
 
@@ -102,7 +102,7 @@ To attach the debugger from Visual Studio and hit breakpoints in client-side cod
 
 1. Switch to Visual Studio and then set a breakpoint in your source code, which might be a JavaScript file, TypeScript file, or a JSX file. (Set the breakpoint in a line of code that allows breakpoints, such as a return statement or a var declaration.)
 
-    ![Set a breakpoint](../javascript/media/tutorial-nodejs-react-set-breakpoint-client-code.png)
+    ![Screenshot of the Visual Studio code window. A return statement is selected and a red dot in the left gutter indicates that a breakpoint is set.](../javascript/media/tutorial-nodejs-react-set-breakpoint-client-code.png)
 
     To find the specific code in a transpiled file, use **Ctrl**+**F** (**Edit** > **Find and Replace** > **Quick Find**).
 

docs/javascript/npm-package-management.md

@@ -50,7 +50,7 @@ For Node.js projects, the easiest way to install npm packages is through the npm
 
 In this window you can search for a package, specify options, and install.
 
-![Search npm package](../javascript/media/search-package.png)
+![Screenshot of the Install New npm Packages dialog. The azure 2.2.1-preview package is selected and the details and options for that package are shown.](../javascript/media/search-package.png)
 
 * **Dependency type** - Chose between **Standard**, **Development**, and **Optional** packages. Standard specifies that the package is a runtime dependency, whereas Development specifies that the package is only required during development.
 * **Add to package.json** - Recommended. This configurable option is deprecated.
@@ -68,7 +68,7 @@ You can see the progress of the installation in the **npm** output in the **Outp
 
 npm packages are shown in Solution Explorer. The entries under the **npm** node mimic the dependencies in the *package.json* file.
 
-![Search npm package](../javascript/media/solution-explorer-status.png)
+![Screenshot of the npm node in Solution Explorer showing the installation status of the npm packages.](../javascript/media/solution-explorer-status.png)
 
 ### Package status
 
@@ -82,12 +82,12 @@ Right-click the **npm** node to take one of the following actions:
 
 * **Install New npm Packages** Opens the UI to install new packages.
 * **Install npm Packages** Runs the npm install command to install all packages listed in *package.json*. (Runs `npm install`.)
-* **Update npm Packages** Updates packages to the latest versions, according to the semantic versioning (semver) range specified in *package.json*. (Runs `npm update --save`.). Semver ranges are typically specified using "~" or "^". For more information, [package.json configuration](../javascript/configure-packages-with-package-json.md).
+* **Update npm Packages** Updates packages to the latest versions, according to the semantic versioning (SemVer) range specified in *package.json*. (Runs `npm update --save`.). SemVer ranges are typically specified using "~" or "^". For more information, [package.json configuration](../javascript/configure-packages-with-package-json.md).
 
 Right-click a package node to take one of the following actions:
 
 * **Install npm Package(s)** Runs the npm install command to install the package version listed in *package.json*. (Runs `npm install`.)
-* **Update npm Package(s)** Updates the package to the latest version, according to the semver range specified in *package.json*. (Run `npm update --save`.) Semver ranges are typically specified using "~" or "^".
+* **Update npm Package(s)** Updates the package to the latest version, according to the SemVer range specified in *package.json*. (Run `npm update --save`.) SemVer ranges are typically specified using "~" or "^".
 * **Uninstall npm Package(s)** Uninstalls the package and removes it from *package.json* (Runs `npm uninstall --save`.)
 ::: moniker-end
 ::: moniker range="vs-2017"
@@ -159,7 +159,7 @@ When you save the file, Visual Studio adds the package under the **Dependencies
 
 For projects with npm included, you can configure npm packages using `package.json`. Right-click the npm node in Solution Explorer and choose **Open package.json**.
 
-![Search npm package](../javascript/media/npm-add-package.png)
+![Screenshot of the Solution Explorer with the npm node selected. A right-click context menu is open and Open package.json is selected.](../javascript/media/npm-add-package.png)
 
 IntelliSense in *package.json* helps you select a particular version of an npm package.