markdig migration

Author: gewarren

docs/debugger/a-dcom-error-occurred-trying-to-contact-the-remote-computer-access-is-denied.md

@@ -26,23 +26,23 @@ ms.workload:
 # A DCOM error occurred trying to contact the remote computer. Access is denied.
 Remote debugging uses DCOM to communicate between the local and remote computers in the following situations:  
 
--   The debugger is set to **Native Compatibility Mode** or **Managed Compatibility Mode** is checked in the **Tools > Options > Debugging** page  
+- The debugger is set to **Native Compatibility Mode** or **Managed Compatibility Mode** is checked in the **Tools > Options > Debugging** page  
 
--   You are debugging managed C++ (C++/CLI) code.  
+- You are debugging managed C++ (C++/CLI) code.  
 
--   In Visual Studio 2013, when **Enable native Edit and Continue** is checked in the **Tools > Options > Debugging** page  
+- In Visual Studio 2013, when **Enable native Edit and Continue** is checked in the **Tools > Options > Debugging** page  
 
--   Some third party debugging scenarios  
+- Some third party debugging scenarios  
 
- This error occurs when the Visual Studio process cannot authenticate itself (or the supplied credentials were deemed insufficient) to the remote debugger process over DCOM. One or more of the following workarounds might resolve the issue:  
+  This error occurs when the Visual Studio process cannot authenticate itself (or the supplied credentials were deemed insufficient) to the remote debugger process over DCOM. One or more of the following workarounds might resolve the issue:  
 
--   Turn off  **Native Compatibility Mode** and **Managed Compatibility Mode**.  
+- Turn off  **Native Compatibility Mode** and **Managed Compatibility Mode**.  
 
--   In Visual Studio 2013, turn off **Enable native Edit and Continue**.  
+- In Visual Studio 2013, turn off **Enable native Edit and Continue**.  
 
--   Reboot both computers.  
+- Reboot both computers.  
 
--   If remote debugging requires entering credentials, check the option to save the credentials.  
+- If remote debugging requires entering credentials, check the option to save the credentials.  
 
 ## See Also  
  [Remote Debugging Errors and Troubleshooting](../debugger/remote-debugging-errors-and-troubleshooting.md)   

docs/debugger/aspnet-debugging-system-requirements.md

@@ -22,13 +22,13 @@ ms.workload:
 # ASP.NET Debugging: System Requirements
 This topic describes the software and security requirements for [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] debugging scenarios:  
 
--   Local debugging, in which [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] and the Web application run on the same computer. There are two versions of this scenario:  
+- Local debugging, in which [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] and the Web application run on the same computer. There are two versions of this scenario:  
 
-    -   The [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] code resides on the file system.  
+  - The [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] code resides on the file system.  
 
-    -   The [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] code resides in an IIS Web site.  
+  - The [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] code resides in an IIS Web site.  
 
--   Remote debugging, in which [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] runs on a client computer and debugs a Web application that is running on a remote server computer.  
+- Remote debugging, in which [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] runs on a client computer and debugs a Web application that is running on a remote server computer.  
 
 ## Security Requirements  
  For remote debugging, local and remote computers must be on a domain setup or a workgroup setup.  

docs/debugger/assertions-in-managed-code.md

@@ -138,19 +138,19 @@ Debug.Assert ( temp != 0 );
 
  Otherwise, for <xref:System.Diagnostics.Trace> methods to work, your program must have one of the following at the top of the source file:  
 
--   `#Const TRACE = True` in Visual Basic  
+- `#Const TRACE = True` in Visual Basic  
 
--   `#define TRACE` in Visual C# and C++  
+- `#define TRACE` in Visual C# and C++  
 
- Or your program must be built with the TRACE option:  
+  Or your program must be built with the TRACE option:  
 
--   `/d:TRACE=True` in Visual Basic  
+- `/d:TRACE=True` in Visual Basic  
 
--   `/d:TRACE` in Visual C# and C++  
+- `/d:TRACE` in Visual C# and C++  
 
- If you need to use the Debug methods in a C# or Visual Basic Release build, you must define the DEBUG symbol in your Release configuration.  
+  If you need to use the Debug methods in a C# or Visual Basic Release build, you must define the DEBUG symbol in your Release configuration.  
 
- C++ does not support the <xref:System.Diagnostics.Debug> class methods. You can achieve the same effect by using the <xref:System.Diagnostics.Trace> class with conditional compilation, such as `#ifdef DEBUG`... `#endif`. You can define these symbols in the **\<Project> Property Pages** dialog box. For more information, see [Changing Project Settings for a Visual Basic Debug Configuration](../debugger/project-settings-for-a-visual-basic-debug-configuration.md) or [Changing Project Settings for a C or C++ Debug Configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md).  
+  C++ does not support the <xref:System.Diagnostics.Debug> class methods. You can achieve the same effect by using the <xref:System.Diagnostics.Trace> class with conditional compilation, such as `#ifdef DEBUG`... `#endif`. You can define these symbols in the **\<Project> Property Pages** dialog box. For more information, see [Changing Project Settings for a Visual Basic Debug Configuration](../debugger/project-settings-for-a-visual-basic-debug-configuration.md) or [Changing Project Settings for a C or C++ Debug Configuration](../debugger/project-settings-for-a-cpp-debug-configuration.md).  
 
 ##  <a name="BKMK_Assert_arguments"></a> Assert arguments  
  <xref:System.Diagnostics.Trace.Assert%2A?displayProperty=fullName> and <xref:System.Diagnostics.Debug.Assert%2A?displayProperty=fullName> take up to three arguments. The first argument, which is mandatory, is the condition you want to check. If you call <xref:System.Diagnostics.Trace.Assert(System.Boolean)?displayProperty=fullName> or <xref:System.Diagnostics.Debug.Assert(System.Boolean)?displayProperty=fullName> with only one argument, the `Assert` method checks the condition and, if the result is false, outputs the contents of the call stack to the **Output** window. The following example shows <xref:System.Diagnostics.Trace.Assert(System.Boolean)?displayProperty=fullName> and <xref:System.Diagnostics.Debug.Assert(System.Boolean)?displayProperty=fullName>:  

docs/debugger/attach-to-running-processes-with-the-visual-studio-debugger.md

@@ -48,30 +48,30 @@ To debug a process on a remote computer, see [Attach to a process on a remote co
 
 **To attach to a process on your local computer:**  
 
-1.  In Visual Studio, select **Debug** > **Attach to Process** (or press **Ctrl**+**Alt**+**P**) to open the **Attach to Process** dialog box.
+1. In Visual Studio, select **Debug** > **Attach to Process** (or press **Ctrl**+**Alt**+**P**) to open the **Attach to Process** dialog box.
 
-  **Connection type** should be set to **Default**. **Connection target** should be your local machine name. 
+   **Connection type** should be set to **Default**. **Connection target** should be your local machine name. 
 
-  ![DBG_Basics_Attach_To_Process](../debugger/media/DBG_Basics_Attach_To_Process.png "DBG_Basics_Attach_To_Process") 
+   ![DBG_Basics_Attach_To_Process](../debugger/media/DBG_Basics_Attach_To_Process.png "DBG_Basics_Attach_To_Process") 
 
-1.  In the **Available processes** list, find and select the process or processes you want to attach to.  
+2. In the **Available processes** list, find and select the process or processes you want to attach to.  
 
-  - To quickly select a process, type its name or first letter in the **Filter processes** box. 
+   - To quickly select a process, type its name or first letter in the **Filter processes** box. 
 
-  - If you don't know the process name, browse through the list, or see [Common debugging scenarios](#BKMK_Scenarios) for some common process names. 
+   - If you don't know the process name, browse through the list, or see [Common debugging scenarios](#BKMK_Scenarios) for some common process names. 
 
-  >[!TIP]
-  >Processes can start and stop in the background while the **Attach to Process** dialog box is open, so the list of running processes may not always be current. You can select **Refresh** at any time to see the current list. 
+   >[!TIP]
+   >Processes can start and stop in the background while the **Attach to Process** dialog box is open, so the list of running processes may not always be current. You can select **Refresh** at any time to see the current list. 
   
-1.  In the **Attach to** field, make sure the type of code you plan to debug is listed. The default **Automatic** setting works for most app types. 
+3. In the **Attach to** field, make sure the type of code you plan to debug is listed. The default **Automatic** setting works for most app types. 
 
-  To select code types manually:
-    1. Click **Select**. 
-    1. In the **Select Code Type** dialog box, select **Debug these code types**.
-    1. Select the code types you want to debug.
-    1. Select **OK**.
+   To select code types manually:
+   1. Click **Select**. 
+   1. In the **Select Code Type** dialog box, select **Debug these code types**.
+   1. Select the code types you want to debug.
+   1. Select **OK**.
 
-1.  Select **Attach**.
+4. Select **Attach**.
 
 >[!NOTE]
 >You can be attached to multiple apps for debugging, but only one app is active in the debugger at a time. You can set the active app in the Visual Studio **Debug Location** toolbar or **Processes** window.  
@@ -84,46 +84,46 @@ For more complete instructions for debugging ASP.NET applications that have been
 
 **To attach to a running process on a remote computer:**  
 
-1.  In Visual Studio, select **Debug** > **Attach to Process** (or press **Ctrl**+**Alt**+**P**) to open the **Attach to Process** dialog box.
+1. In Visual Studio, select **Debug** > **Attach to Process** (or press **Ctrl**+**Alt**+**P**) to open the **Attach to Process** dialog box.
 
-1.  **Connection type** should be **Default** for most cases. In the **Connection target** box, select the remote computer, using one of the following methods:
+2. **Connection type** should be **Default** for most cases. In the **Connection target** box, select the remote computer, using one of the following methods:
 
-  - Select the drop-down arrow next to **Connection target**, and select the computer name from the drop-down list.  
-  - Type the computer name in the **Connection target** box.
+   - Select the drop-down arrow next to **Connection target**, and select the computer name from the drop-down list.  
+   - Type the computer name in the **Connection target** box.
 
-      > [!NOTE]
-      > If you can't connect using the remote computer name, try using the IP and port address (for example, `123.45.678.9:4022`). 4022 is the default port for the Visual Studio 2017 x64 remote debugger. For other remote debugger port assignments, see [Remote debugger port assignments](remote-debugger-port-assignments.md).  
+     > [!NOTE]
+     > If you can't connect using the remote computer name, try using the IP and port address (for example, `123.45.678.9:4022`). 4022 is the default port for the Visual Studio 2017 x64 remote debugger. For other remote debugger port assignments, see [Remote debugger port assignments](remote-debugger-port-assignments.md).  
       
-  - Select the **Find** button next to the **Connection target** box to open the **Remote Connections** dialog box. The **Remote Connections** dialog box lists all the devices that are on your local subnet or directly attached to your computer. You may need to [open UDP port 3702](../debugger/remote-debugger-port-assignments.md) on the server to discover remote devices. Select the computer or device you want, and then click **Select**. 
+   - Select the **Find** button next to the **Connection target** box to open the **Remote Connections** dialog box. The **Remote Connections** dialog box lists all the devices that are on your local subnet or directly attached to your computer. You may need to [open UDP port 3702](../debugger/remote-debugger-port-assignments.md) on the server to discover remote devices. Select the computer or device you want, and then click **Select**. 
 
-  > [!NOTE]
-  > The **Connection type** setting persists between debugging sessions. The **Connection target** setting persists between debugging sessions only if a successful debugging connection occurred with that target.
+   > [!NOTE]
+   > The **Connection type** setting persists between debugging sessions. The **Connection target** setting persists between debugging sessions only if a successful debugging connection occurred with that target.
 
-1.  Click **Refresh** to populate the **Available processes** list.
+3. Click **Refresh** to populate the **Available processes** list.
 
-     >[!TIP]
-     >Processes can start and stop in the background while the **Attach to Process** dialog box is open, so the list of running processes may not always be current. You can select **Refresh** at any time to see the current list. 
+    >[!TIP]
+    >Processes can start and stop in the background while the **Attach to Process** dialog box is open, so the list of running processes may not always be current. You can select **Refresh** at any time to see the current list. 
      
-1.  In the **Available processes** list, find and select the process or processes you want to attach to.  
+4. In the **Available processes** list, find and select the process or processes you want to attach to.  
 
-  - To quickly select a process, type its name or first letter in the **Filter processes** box. 
+   - To quickly select a process, type its name or first letter in the **Filter processes** box. 
 
-  - If you don't know the process name, browse through the list, or see [Common debugging scenarios](#BKMK_Scenarios) for some common process names. 
+   - If you don't know the process name, browse through the list, or see [Common debugging scenarios](#BKMK_Scenarios) for some common process names. 
 
-  - To find processes running under all user accounts, select the **Show processes from all users** check box.
+   - To find processes running under all user accounts, select the **Show processes from all users** check box.
 
-      >[!NOTE]
-      >If you try to attach to a process owned by an untrusted user account, a security warning dialog box confirmation will appear. For more information see [Security Warning: Attaching to a process owned by an untrusted user can be dangerous. If the following information looks suspicious or you are unsure, do not attach to this process](../debugger/security-warning-attaching-to-a-process-owned-by-an-untrusted-user.md).  
+     >[!NOTE]
+     >If you try to attach to a process owned by an untrusted user account, a security warning dialog box confirmation will appear. For more information see [Security Warning: Attaching to a process owned by an untrusted user can be dangerous. If the following information looks suspicious or you are unsure, do not attach to this process](../debugger/security-warning-attaching-to-a-process-owned-by-an-untrusted-user.md).  
       
-1.  In the **Attach to** field, make sure the type of code you plan to debug is listed. The default **Automatic** setting works for most app types. 
+5. In the **Attach to** field, make sure the type of code you plan to debug is listed. The default **Automatic** setting works for most app types. 
 
-  To select code types manually:
-    1. Click **Select**. 
-    1. In the **Select Code Type** dialog box, select **Debug these code types**.
-    1. Select the code types you want to debug.
-    1. Select **OK**.
+   To select code types manually:
+   1. Click **Select**. 
+   1. In the **Select Code Type** dialog box, select **Debug these code types**.
+   1. Select the code types you want to debug.
+   1. Select **OK**.
 
-1.  Select **Attach**.
+6. Select **Attach**.
 
 >[!NOTE]
 >You can be attached to multiple apps for debugging, but only one app is active in the debugger at a time. You can set the active app in the Visual Studio **Debug Location** toolbar or **Processes** window.