Merge branch 'regexp' of github.com:ghogen/vsdocs into regexp

Author: ghogen

docs/azure/vs-azure-tools-azure-project-create.md

@@ -28,7 +28,6 @@ This section walks you through creating an Azure cloud service project in Visual
 
    ![Give the project a name](./media/vs-azure-tools-azure-project-create/vs-2019/new-project-cloud-service-2.png)
 
-
 1. In the **New Microsoft Azure Cloud Service** dialog, select the roles that you want to add, and choose the right arrow button to add them to your solution.
 
     ![Select new Azure cloud service roles](./media/vs-azure-tools-azure-project-create/new-cloud-service.png)

docs/code-quality/code-metrics-values.md

@@ -47,7 +47,6 @@ The following list shows the code metrics results that Visual Studio calculates:
 - **Lines of Executable code** - Indicates the approximate number of executable code lines or operations. This is a count of number of operations in executable code. This metric is available starting in Visual Studio 2019 version 16.4 and Microsoft.CodeAnalysis.Metrics (2.9.5). The value is typically a close match to the previous metric, **Lines of Code**, which is the MSIL-instruction-based metric used in legacy mode.
 
 
-
 ## Anonymous methods
 
 An *anonymous method* is just a method that has no name. Anonymous methods are most frequently used to pass a code block as a delegate parameter. Code metrics results for an anonymous method that's declared in a member, such as a method or accessor, are associated with the member that declares the method. They are not associated with the member that calls the method.

docs/code-quality/how-to-generate-code-metrics-data.md

@@ -255,7 +255,6 @@ The new command-line code metrics tool computes metrics even in the presence of
 Starting in Visual Studio 2019 version 16.4 and Microsoft.CodeAnalysis.Metics (2.9.5), `SourceLines` and `ExecutableLines` replace the previous `LinesOfCode` metric. For descriptions of the new metrics, see [Code metrics values](../code-quality/code-metrics-values.md). The `LinesOfCode` metric is available in legacy mode.
 
 
-
 Other metrics such as `CyclomaticComplexity` and `MaintainabilityIndex` use the same formulas as previous versions of *Metrics.exe*, but the new tool counts the number of `IOperations` (logical source instructions) instead of intermediate language (IL) instructions. The numbers will be slightly different to those generated by the Visual Studio IDE and by previous versions of *Metrics.exe*.
 
 ## See also

docs/code-quality/in-source-suppression-overview.md

@@ -46,7 +46,6 @@ You can suppress violations in code using a preprocessor directive, the [#pragma
 
   :::image type="content" source="media/vs-2019/suppress-diagnostic-from-editor-attribute.png" alt-text="Suppress diagnostic from quick actions menu using attribute":::
 
-
 - From the **Error List**
 
   Select the rules you want to suppress, and then right-click and select **Suppress** > **In Source**.

docs/containers/container-tools-react.md

@@ -19,7 +19,6 @@ You can run and debug your apps in Linux or Windows containers running on your l
 
 This article illustrates how to use Visual Studio to start an app in a local Docker container, make changes, and then refresh the browser to see the changes. This article also shows you how to set breakpoints for debugging for containerized apps. Supported project types include web app, console app, and Azure Function targeting .NET Framework and .NET Core. The examples presented in this article, are a project of type ASP.NET Core Web App and a project of type Console App (.NET Framework).
 
-
 If you already have a project of a supported type, Visual Studio can create a Dockerfile and configure your project to run in a container. See [Container Tools in Visual Studio](overview.md).
 
 ## Prerequisites

docs/containers/edit-and-refresh.md

@@ -197,7 +197,6 @@ With Service Fabric tools in Visual Studio, you can develop and debug for Azure
 
 Visual Studio 2019 and later support developing containerized microservices using Windows containers and Service Fabric orchestration.
 
-
 For a detailed tutorial, see
 [Tutorial: Deploy a .NET application in a Windows container to Azure Service Fabric](/azure/service-fabric/service-fabric-host-app-in-a-container).
 

docs/containers/media/container-tools-react/vs-2022/debugging-aspnet-core.png

@@ -24,7 +24,6 @@ ms.workload:
 > [!NOTE]
 > The features described in this article apply to .NET Framework Windows Forms and WPF development. The features are not supported for .NET Core development, for both WPF and Windows Forms.
 
-
 In the context of .NET data tools in Visual Studio, the term *data source* refers to .NET objects that connect to a data store and make the data available to a .NET application. The Visual Studio designers can consume the output of the data source to generate the boilerplate code that binds the data to forms when you drag and drop database objects from the **Data Sources** window. This kind of data source can be:
 
 - A class in an Entity Framework model that is associated with some kind of database.

docs/containers/media/container-tools-react/vs-2022/debugging-client-javascript.png

@@ -26,7 +26,6 @@ For .NET Framework projects, *service reference* enables a project to access one
 
 For .NET Core projects, you can use the **Connected Services** node in **Solution Explorer** to access the **Microsoft WCF Web Service Reference Provider**, which lets you manage Windows Communication Foundation (WCF) data service references.
 
-
 [!INCLUDE[note_settings_general](../data-tools/includes/note_settings_general_md.md)]
 
 ## Prerequisites
@@ -87,7 +86,6 @@ The WCF tools are not installed with the .NET workload; use the Visual Studio In
 
      A service client (proxy) is generated, and metadata that describes the service is added to the *app.config* file.
 
-
 ### To add a reference to a service in the current solution (.NET Framework projects)
 
 1. In **Solution Explorer**, right-click the name of the project to which you want to add the service, and then click **Add Service Reference**.

docs/containers/media/container-tools-react/vs-2022/launch-profiles-debugging-docker.png

@@ -111,7 +111,6 @@ In the debugger side code, edit the <xref:System.Diagnostics.DebuggerVisualizerA
 
 The debuggee side code contains the object source that gets visualized. The data object can override methods of <xref:Microsoft.VisualStudio.DebuggerVisualizers.VisualizerObjectSource>. A debuggee side DLL is necessary if you want to create a standalone visualizer.
 
-
 In the debuggee-side code:
 
 - To let the visualizer edit data objects, the object source must inherit from from <xref:Microsoft.VisualStudio.DebuggerVisualizers.VisualizerObjectSource> and override the `TransferData` or `CreateReplacementObject` methods.

docs/containers/media/container-tools-react/vs-2022/launch-profiles-debugging.png

@@ -37,7 +37,6 @@ In this tutorial, you will:
    If it's not already installed, install [Visual Studio 2019](https://visualstudio.microsoft.com/downloads). If you're updating from a previous Visual Studio installation, run the Visual Studio Installer and check the Snapshot Debugger component in the **ASP.NET and web development workload**.
 
 
-
 * Basic or higher Azure App Service plan.
 
 * Snapshot collection is available for the following web apps running in Azure App Service:
@@ -65,7 +64,6 @@ In this tutorial, you will:
    > [!NOTE]
    > (Visual Studio 2019 version 16.2 and above) Snapshot Debugger has enabled Azure cloud support. Make sure that both the Azure resource and Azure Storage account you select are from the same cloud. Please contact your Azure administrator if you have questions about your enterprise's [Azure compliance](https://azure.microsoft.com/overview/trusted-cloud/) configurations.
 
-
    Visual Studio is now in snapshot debugging mode.
    ![Snapshot debugging mode](../debugger/media/snapshot-message.png)
 

docs/containers/overview.md

@@ -53,7 +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!
 
-
 1. Open Visual Studio.
 
    If the start window is not open, choose **File** > **Start Window**.
@@ -78,7 +77,6 @@ First, you'll create a C++ console application project. The project type comes w
 
    Visual Studio opens your new project.
 
-
 ## Create the application
 
 1. In *get-started-debugging.cpp*, replace all of the default code with the following code instead:

docs/data-tools/add-new-data-sources.md

@@ -63,7 +63,6 @@ If you already have your own Direct3D app to explore Graphics Diagnostics with,
 Download a sample from [Direct3D Game Sample](/samples/microsoft/windows-universal-samples/simple3dgamedx/).
 
 
-
 Make sure you can build and run the app before moving on. Choose **Build** > **Build Solution** to make sure it builds without errors. Then choose **Debug** > **Start without Debugging** (**Ctrl + F5**) to make sure it runs correctly. Depending on what machine you are testing with the tool, you may need to adjust the platform and debugging target for the sample. For example, to test against the x64 platform on your Visual Studio host machine, choose **x64** as the Solution Platform and **Local Machine** as your debugging target. 
 
 ### 2 - Start a Graphics Diagnostics session

docs/data-tools/how-to-add-update-or-remove-a-wcf-data-service-reference.md

@@ -63,7 +63,6 @@ If you have Visual Studio installed, but don't have the workloads you need, sele
     Press **Esc** to close the start window. Type **Ctrl + Q** to open the search box, type **Empty Project**, choose **Templates**, then choose **Empty Project** for C++. In the dialog box that appears, choose **Create**. Then, type a name like **Mixed_Mode_Debugging** and click **Create**.
 
 
-
     If you don't see the **Empty Project** project template, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. The Visual Studio Installer launches. Choose the **Desktop development with C++** workload, then choose **Modify**.
 
     Visual Studio creates the project.
@@ -135,7 +134,6 @@ If you have Visual Studio installed, but don't have the workloads you need, sele
     For .NET Core, choose either the recommended target framework or .NET 6, and then choose **Create**.
 
 
-
     If you don't see the correct project template, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. Choose the correct .NET workload as described in the prerequisites, and then choose **Modify**.
 
     > [!NOTE]

docs/debugger/create-custom-visualizers-of-data.md

@@ -65,7 +65,6 @@ After you have created a visualizer, you must install the visualizer so that it
 > The procedure is different in Visual Studio 2017 and older. See the [previous version](how-to-install-a-visualizer.md?view=vs-2017&preserve-view=true) of this article.
 
 
-
 ## See also
 - [Create Custom Visualizers](../debugger/create-custom-visualizers-of-data.md)
 - [How to: Write a Visualizer](create-custom-visualizers-of-data.md)

docs/debugger/debug-live-azure-applications.md

@@ -27,7 +27,6 @@ The Visual Studio debugger provides many powerful features to help you debug you
     Press **Esc** to close the start window. Type **Ctrl + Q** to open the search box, type **asp.net**, choose **Templates**, then choose **Create new ASP.NET Core Web Application**. In the dialog box that appears, choose **Create**.
 
 
-
     If you don't see the **ASP.NET Core Web Application** project template, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. Choose the **ASP.NET and web development** workload, then choose **Modify**.
 
     Visual Studio creates the project.

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

@@ -27,7 +27,6 @@ The Visual Studio debugger provides many powerful features to help you debug you
     Press **Esc** to close the start window. Type **Ctrl + Q** to open the search box, type **c++**, choose **Templates**, then choose **Create new Console App project**. In the dialog box that appears, choose **Create**.
 
 
-
     If you don't see the **Windows Console Application** project template, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. The Visual Studio Installer launches. Choose the **Desktop development with C++** workload, then choose **Modify**.
 
     Visual Studio creates the project.

docs/debugger/graphics/getting-started-with-visual-studio-graphics-diagnostics.md

@@ -35,7 +35,6 @@ The Visual Studio debugger provides many powerful features to help you debug you
     If you don't see the **Console App** project template for .NET Core, go to **Tools** > **Get Tools and Features...**, which opens the Visual Studio Installer. Choose the **.NET Core cross-platform development** workload, then choose **Modify**.
 
 
-
     Visual Studio creates the project.
 
 1. In *Program.cs* or *Module1.vb*, replace the following code

docs/debugger/how-to-debug-managed-and-native-code.md

@@ -29,7 +29,6 @@ This guide explains how to set up and configure a Visual Studio ASP.NET MVC 4.5.
 
 Visual Studio 2019 is required to follow the steps shown in this article.
 
-
 These procedures have been tested on these server configurations:
 
 * Windows Server 2012 R2 and IIS 8 (For Windows Server 2008 R2, the server steps are different)
@@ -56,7 +55,6 @@ This article includes steps on setting up a basic configuration of IIS on Window
     In Visual Studio 2019, type **Ctrl + Q** to open the search box, type **asp.net**, choose **Templates**, then choose **Create new ASP.NET Web Application (.NET Framework)**. In the dialog box that appears, name the project **MyASPApp**, and then choose **Create**. Select **MVC** and choose **Create**.
 
 
-
 2. Open the  *HomeController.cs* file, and set a breakpoint in the `About()` method.
 
 ## <a name="bkmk_configureIIS"></a> Install and Configure IIS on Windows Server
@@ -125,7 +123,6 @@ After the app deploys successfully, it should start automatically. If the app do
    Choose **Edit** to edit the profile, and then choose **Settings**. Choose a **Debug** configuration, and then choose **Remove additional files at destination** under the **File Publish** options.
 
 
-
    > [!IMPORTANT]
    > If you choose a Release configuration, you disable debugging in the *web.config* file when you publish.
 
@@ -224,7 +221,6 @@ For information on running the remote debugger as a service, see [Run the remote
     ![RemoteDBG_AttachToProcess](../debugger/media/vs-2019/remotedbg-attachtoprocess.png "RemoteDBG_AttachToProcess")
 
 
-
 7. Click **Attach**
 
 8. Open the remote computer's website. In a browser, go to **http://\<remote computer name>**.
@@ -262,7 +258,6 @@ Required ports:
 
 * 4024 - Required for remote debugging from Visual Studio 2019 (see [Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments.md) for more information).
 
-
 * UDP 3702 - (Optional) Discovery port enables you to the **Find** button when attaching to the remote debugger in Visual Studio.
 
 1. To open a port on Windows Server, open the **Start** menu, search for **Windows Firewall with Advanced Security**.

docs/debugger/how-to-install-a-visualizer.md

@@ -28,7 +28,6 @@ This guide explains how to set up and configure a Visual Studio ASP.NET Core, de
 Visual Studio 2019 is required to follow the steps shown in this article.
 
 
-
 These procedures have been tested on these server configurations:
 * Windows Server 2012 R2 and IIS 8
 * Windows Server 2016 and IIS 10
@@ -55,7 +54,6 @@ This article includes steps on setting up a basic configuration of IIS on Window
     Choose either the recommended target framework or .NET 6, and then choose **Create**.
 
 
-
 4. Open the About.cshtml.cs file and set a breakpoint in the `OnGet` method (in older templates, open HomeController.cs instead and set the breakpoint in the `About()` method).
 
 ## <a name="bkmk_configureIIS"></a> Install and Configure IIS on Windows Server
@@ -125,7 +123,6 @@ After the app deploys successfully, it should start automatically. If the app do
    Choose **Edit** to edit the profile, and then choose **Settings**. Choose a **Debug** configuration, and then choose **Remove additional files at destination** under the **File Publish** options.
 
 
-
    > [!IMPORTANT]
    > If you choose a Release configuration, you disable debugging in the *web.config* file when you publish.
 
@@ -217,7 +214,6 @@ For information on running the remote debugger as a service, see [Run the remote
     ![RemoteDBG_AttachToProcess](../debugger/media/vs-2019/remotedbg-attachtoprocess-aspnetcore.png "RemoteDBG_AttachToProcess")
 
 
-
 7. Click **Attach**.
 
 8. Open the remote computer's website. In a browser, go to **http://\<remote computer name>**.

docs/debugger/quickstart-debug-aspnet.md

@@ -42,7 +42,6 @@ These procedures have been tested on these server configurations:
 Visual Studio 2019 or later versions is required to follow the steps shown in this article.
 
 
-
 ### Network requirements
 
 Debugging between two computers connected through a proxy is not supported. Debugging over a high latency or low bandwidth connection, such as dialup Internet, or over the Internet across countries is not recommended and may fail or be unacceptably slow. For a complete list of requirements, see [Requirements](../debugger/remote-debugging.md#requirements_msvsmon).
@@ -68,7 +67,6 @@ This article includes steps on setting up a basic configuration of IIS on Window
     Choose either the recommended target framework or .NET 6, and then choose **Create**.
 
 
-
 1. Open the About.cshtml.cs file and set a breakpoint in the `OnGet` method (in older templates, open HomeController.cs instead and set the breakpoint in the `About()` method).
 
 ## Update browser security settings on Windows Server
@@ -217,7 +215,6 @@ Download the version of the remote tools that matches your version of Visual Stu
     ![RemoteDBG_AttachToProcess](../debugger/media/vs-2019/remotedbg-attachtoprocess-aspnetcore.png "RemoteDBG_AttachToProcess")
 
 
-
 7. Click **Attach**.
 
 8. Open the remote computer's website. In a browser, go to **http://\<remote computer name>**.

docs/debugger/quickstart-debug-with-cplusplus.md

@@ -55,7 +55,6 @@ From the list provided, choose the type(s) of code you want to debug. This can b
 - Unity - Unity
 - Managed Compatibility Mode - Specifies the legacy debugger for managed code, for use typically in mixed-mode debugging with C++/CLR code (enables Edit and Continue for mixed mode) or to support extensions that targeted the legacy debugger. In most mixed-mode debugging scenarios, select **Native** and the appropriate **Managed** code types instead of Managed Compatibility Mode.
 
-
 For most scenarios, attaching multiple debuggers in the same debugging session is not supported. You may be able to do this using a second instance of Visual Studio.
 
 ## See also

docs/debugger/quickstart-debug-with-managed.md

@@ -48,7 +48,6 @@ This article describes how to start a Visual Studio debugging session for a Univ
 > Starting in Visual Studio 2019, UWP apps for HTML and JavaScript are no longer supported.
 
 
-
 ## <a name="BKMK_The_easy_way_to_start_debugging"></a>Start debugging from the Visual Studio toolbar
 
 The easiest way to configure and start debugging is from the standard Visual Studio toolbar.

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

@@ -41,7 +41,6 @@ Follow the tasks below to create a visualizer.
     For the visualizer project, make sure you select a .NET Framework class library and not .NET. Although the visualizer needs to be .NET Framework, the calling app can be .NET.
 
 
-
    After you have created the class library, you must add a reference to Microsoft.VisualStudio.DebuggerVisualizers.DLL so that you can use the classes defined there. Before you add the reference, however, you must rename some classes so that they have meaningful names.
 
 ### To rename Class1.cs and add Microsoft.VisualStudio.DebuggerVisualizers
@@ -174,7 +173,6 @@ In the debugger-side code, you specify the type to visualize (the object source)
     > If you want to easily test the visualizer using a test harness, create a .NET Framework console app. You can create a .NET console app instead, but the test harness described later is not yet supported for .NET, so you will need to install the visualizer to test it. For a .NET console app, first create the console app here, add the required DLL and project references, and then follow steps described in [Add a debuggee-side data object](#add-a-debuggee-side-data-object). For ASP.NET Core scenarios, see [Special debugger side considerations for .NET 5.0+](../debugger/create-custom-visualizers-of-data.md#special-debugger-side-considerations-for-net-50).
 
 
-
    Now, you must add the necessary references so MyTestConsole can call MyFirstVisualizer.
 
 ### To add necessary references to MyTestConsole