Merge pull request #5720 from gewarren/links-clean-up

Links clean up

Author: Jak-MS

docs/code-quality/ca1053.md

@@ -25,7 +25,7 @@ ms.workload:
 |Breaking change|Breaking|
 
 > [!NOTE]
-> Rule CA1053 is combined into [CA1052: Static holder types should be sealed](ca1052-static-holder-types-should-be-sealed.md) in [FxCop analyzers](fxcop-analyzers.yml).
+> Rule CA1053 is combined into [CA1052: Static holder types should be sealed](ca1052.md) in [FxCop analyzers](fxcop-analyzers.yml).
 
 ## Cause
 

docs/code-quality/ca1903.md

@@ -43,7 +43,7 @@ New members and types were included in .NET Framework 2.0 Service Pack 1 and 2,
 |.NET Framework 3.5|.NET Framework 3.5 SP1|
 |.NET Framework 4|N/A|
 
-To change a project's target framework, see [How to: Target a version of .NET](../ide/how-to-target-a-version-of-the-dotnet-framework.md).
+To change a project's target framework, see [How to: Target a version of .NET](../ide/visual-studio-multi-targeting-overview.md).
 
 ## How to fix violations
 To remove the dependency on the service pack, remove all usages of the new member or type. If this is a deliberate dependency, either suppress the warning or turn off this rule.

docs/code-quality/code-analysis-warnings-for-managed-code-by-checkid.md

@@ -270,7 +270,7 @@ The following table lists Code Analysis warnings for managed code by the CheckId
 
 | CheckId | Warning | Description |
 |---------| - | - |
-| CA2007 | [CA2007: Do not directly await a Task](ca2007-do-not-directly-await-task.md) | An asynchronous method [awaits](/dotnet/csharp/language-reference/keywords/await) a <xref:System.Threading.Tasks.Task> directly. When an asynchronous method awaits a <xref:System.Threading.Tasks.Task> directly, continuation occurs in the same thread that created the task. This behavior can be costly in terms of performance and can result in a deadlock on the UI thread. Consider calling <xref:System.Threading.Tasks.Task.ConfigureAwait(System.Boolean)?displayProperty=nameWithType> to signal your intention for continuation. |
+| CA2007 | [CA2007: Do not directly await a Task](ca2007.md) | An asynchronous method [awaits](/dotnet/csharp/language-reference/keywords/await) a <xref:System.Threading.Tasks.Task> directly. When an asynchronous method awaits a <xref:System.Threading.Tasks.Task> directly, continuation occurs in the same thread that created the task. This behavior can be costly in terms of performance and can result in a deadlock on the UI thread. Consider calling <xref:System.Threading.Tasks.Task.ConfigureAwait(System.Boolean)?displayProperty=nameWithType> to signal your intention for continuation. |
 | CA1000 | [CA1000: Do not declare static members on generic types](../code-quality/ca1000.md) | When a static member of a generic type is called, the type argument must be specified for the type. When a generic instance member that does not support inference is called, the type argument must be specified for the member. In these two cases, the syntax for specifying the type argument is different and easily confused. |
 | CA1001 | [CA1001: Types that own disposable fields should be disposable](../code-quality/ca1001.md) | A class declares and implements an instance field that is a System.IDisposable type, and the class does not implement IDisposable. A class that declares an IDisposable field indirectly owns an unmanaged resource and should implement the IDisposable interface. |
 | CA1002 | [CA1002: Do not expose generic lists](../code-quality/ca1002.md) | System.Collections.Generic.List<(Of \<(T>)>) is a generic collection that is designed for performance, not inheritance. Therefore, List does not contain any virtual members. The generic collections that are designed for inheritance should be exposed instead. |

docs/code-quality/fxcop-analyzer-options.md

@@ -32,7 +32,7 @@ These configuration options are available starting in version 2.6.3 of the [Micr
 
 | Description | Allowable values | Default value | Configurable rules |
 | - | - | - | - |
-| Whether to ignore asynchronous methods that don't return a value | `true`<br/>`false` | `false` | [CA2007](ca2007-do-not-directly-await-task.md) |
+| Whether to ignore asynchronous methods that don't return a value | `true`<br/>`false` | `false` | [CA2007](ca2007.md) |
 
 > [!NOTE]
 > In version 2.6.3 and earlier of the analyzer package, this option was named `skip_async_void_methods`.
@@ -50,4 +50,4 @@ These configuration options are available starting in version 2.6.3 of the [Micr
 
 | Description | Allowable values | Default value | Configurable rules |
 | - | - | - | - |
-| Specifies that code in a project that generates this type of assembly should be analyzed | One or more fields of the <xref:Microsoft.CodeAnalysis.OutputKind> enumeration<br/><br/>Separate multiple values with a comma (,) | All output kinds | [CA2007](ca2007-do-not-directly-await-task.md) |
+| Specifies that code in a project that generates this type of assembly should be analyzed | One or more fields of the <xref:Microsoft.CodeAnalysis.OutputKind> enumeration<br/><br/>Separate multiple values with a comma (,) | All output kinds | [CA2007](ca2007.md) |

docs/code-quality/fxcop-rule-port-status.md

@@ -281,7 +281,7 @@ The following FxCop legacy analysis rules are deprecated and won't be implemente
 - [CA1504](ca1504-review-misleading-field-names.md)
 - [CA1701](ca1701-resource-string-compound-words-should-be-cased-correctly.md)
 - [CA1702](ca1702-compound-words-should-be-cased-correctly.md)
-- [CA1703](ca1703-resource-strings-should-be-spelled-correctly.md)
+- [CA1703](ca1703.md)
 - [CA1800](ca1800.md)
 - [CA1809](ca1809.md)
 - [CA1901](ca1901.md)

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

@@ -27,7 +27,7 @@ You can generate code metrics data in three ways:
 The [FxCopAnalyzers NuGet package](https://www.nuget.org/packages/Microsoft.CodeAnalysis.FxCopAnalyzers) includes several code metrics [analyzer](roslyn-analyzers-overview.md) rules:
 
 - [CA1501](ca1501-avoid-excessive-inheritance.md)
-- [CA1502](ca1502-avoid-excessive-complexity.md)
+- [CA1502](ca1502.md)
 - [CA1505](ca1505-avoid-unmaintainable-code.md)
 - [CA1506](ca1506-avoid-excessive-class-coupling.md)
 
@@ -54,7 +54,7 @@ You can configure the thresholds at which the code metrics rules in the FxCop an
    CA1502: 10
    ```
 
-   In this example, rule [CA1502](ca1502-avoid-excessive-complexity.md) is configured to fire when a method's cyclomatic complexity is greater than 10.
+   In this example, rule [CA1502](ca1502.md) is configured to fire when a method's cyclomatic complexity is greater than 10.
 
 3. In the **Properties** window of Visual Studio, or in the project file, mark the build action of the configuration file as [**AdditionalFiles**](../ide/build-actions.md#build-action-values). For example:
 

docs/containers/container-tools-configure.md

@@ -65,4 +65,4 @@ The following table describes **Single Project** and **Docker Compose** settings
 
 ## Next steps
 
-Read more about working with containers in Visual Studio in this [overview](visual-studio-tools-for-docker.md).
+Read more about working with containers in Visual Studio in this [overview](overview.md).

docs/containers/deploy-app-service.md

@@ -87,4 +87,4 @@ Set up continuous integration and delivery (CI/CD) with [Azure Pipelines](/azure
 
 ## See also
 
-[Deploy to Azure Container Registry](vs-azure-tools-docker-hosting-web-apps-in-docker.md)
+[Deploy to Azure Container Registry](hosting-web-apps-in-docker.md)

docs/containers/deploy-docker-hub.md

@@ -39,7 +39,7 @@ If you don't have a Docker Hub repository, create one at [Docker Hub](https://hu
 
 ## Next steps
 
-Publish to [Azure Container Registry](/azure/container-registry/) by following the steps at [Deploy to Azure Container Registry](vs-azure-tools-docker-hosting-web-apps-in-docker.md).
+Publish to [Azure Container Registry](/azure/container-registry/) by following the steps at [Deploy to Azure Container Registry](hosting-web-apps-in-docker.md).
 
 Set up continuous integration and delivery (CI/CD) with [Azure Pipelines](/azure/devops/pipelines/?view=azure-devops).
 

docs/containers/overview.md

@@ -145,4 +145,4 @@ For further details on the services implementation and use of Visual Studio tool
 
 [Debugging apps in a local Docker container](vs-azure-tools-docker-edit-and-refresh.md)
 
-[Deploy an ASP.NET container to a container registry using Visual Studio](vs-azure-tools-docker-hosting-web-apps-in-docker.md)
+[Deploy an ASP.NET container to a container registry using Visual Studio](hosting-web-apps-in-docker.md)

docs/containers/tutorial-kubernetes-tools.md

@@ -133,7 +133,7 @@ To do this, you first need to double-check that you've installed everything as d
 
    ![Screenshot of Publish menu item](media/tutorial-kubernetes-tools/k8s-tools-publish-project.png)
 
-2. In the **Publish** screen, choose **Container Registry** as the publish target, and follow the prompts to select your container registry. If you don't already have a container registry, choose **Create New Azure Container Registry** to create one from Visual Studio. For more information, see [Publish your container to Azure Container Registry](vs-azure-tools-docker-hosting-web-apps-in-docker.md).
+2. In the **Publish** screen, choose **Container Registry** as the publish target, and follow the prompts to select your container registry. If you don't already have a container registry, choose **Create New Azure Container Registry** to create one from Visual Studio. For more information, see [Publish your container to Azure Container Registry](hosting-web-apps-in-docker.md).
 
    ![Screenshot of Pick a publish target screen](media/tutorial-kubernetes-tools/k8s-tools-publish-to-acr.png)
 

docs/containers/view-and-diagnose-containers.md

@@ -26,7 +26,7 @@ The **Containers** window opens automatically when you start a containerized .NE
 On the left side, you see the list of containers on your local machine. The containers associated with your solution are shown under **Solution Containers**. To the right, you see a pane with tabs for **Environment**, **Ports**, **Logs**, and **Files**.
 
 > [!TIP]
-> You can easily customize where the **Containers** tool window is docked in Visual Studio. See [Customizing window layouts in Visual Studio](/visualstudio/ide/customizing-window-layouts-in-visual-studio). By default, the **Containers** window is docked with the **Watch** window when the debugger is running.
+> You can easily customize where the **Containers** tool window is docked in Visual Studio. See [Customizing window layouts in Visual Studio](../ide/customizing-window-layouts-in-visual-studio.md). By default, the **Containers** window is docked with the **Watch** window when the debugger is running.
 
 ## View environment variables
 

docs/debugger/client-side-script-debugging.md

@@ -55,7 +55,7 @@ You can see lists of server-side and client-side script documents in the **Solut
 
 ## See also
 
-- [Debugging ASP.NET and AJAX Applications](/visualstudio/debugger/how-to-enable-debugging-for-aspnet-applications)
+- [Debugging ASP.NET and AJAX Applications](how-to-enable-debugging-for-aspnet-applications.md)
 - [Limitations on Script Debugging](../debugger/limitations-on-script-debugging.md)
 - [Variable Windows](../debugger/debugger-windows.md)
 - [Immediate Window](../ide/reference/immediate-window.md)

docs/debugger/com-and-activex-debugging.md

@@ -44,4 +44,4 @@ This section provides tips on debugging COM applications and ActiveX controls.
 - [Debugger Security](../debugger/debugger-security.md)
 - [Introduction to COM](/cpp/atl/introduction-to-com)
 - [ActiveX Controls](/cpp/mfc/activex-controls)
-- [SDI Server Applications](../debugger/sdi-server-applications.md)
+- [SDI Server Applications](com-server-and-container-debugging.md)

docs/debugger/create-custom-views-of-managed-objects.md

@@ -35,10 +35,10 @@ In .NET Framework 2.0 code, Visual Basic does not support the DebuggerBrowsable
 
 ## Visualizers
 
-You can write a visualizer to display any managed data type. For more information, see [How to: Write a Visualizer](/visualstudio/debugger/create-custom-visualizers-of-data).
+You can write a visualizer to display any managed data type. For more information, see [How to: Write a Visualizer](create-custom-visualizers-of-data.md).
 
 > [!NOTE]
-> For C++ code, you can add custom data type expansions using the Natvis framework, as described in [Create custom views of C++ objects in the debugger](/visualstudio/debugger/create-custom-views-of-native-objects).
+> For C++ code, you can add custom data type expansions using the Natvis framework, as described in [Create custom views of C++ objects in the debugger](create-custom-views-of-native-objects.md).
 
 ## See also
 

docs/debugger/debug-a-webview-control.md

@@ -54,7 +54,7 @@ ms.workload:
 
      The DOM Explorer associated with the `WebView` appears as a new tab in Visual Studio.
 
-5. View and modify live DOM elements and CSS styles as described in [Debug CSS styles using DOM Explorer](/visualstudio/debugger/quickstart-debug-html-and-css).
+5. View and modify live DOM elements and CSS styles as described in [Debug CSS styles using DOM Explorer](quickstart-debug-html-and-css.md).
 
 ### Use the JavaScript Console window to inspect and debug a WebView control
 

docs/debugger/debug-using-the-just-in-time-debugger.md

@@ -98,7 +98,7 @@ This example walks you through Just-In-Time debugging when an app throws an erro
 
 For this example, you'll make a C# console app in Visual Studio that throws a [NullReferenceException](/dotnet/api/system.nullreferenceexception).
 
-1. In Visual Studio, create a C# console app (**File** > **New** > **Project** > **Visual C#** > **Console Application**) named *ThrowsNullException*. For more information about creating projects in Visual Studio, see [Walkthrough: Create a simple application](/visualstudio/get-started/csharp/tutorial-wpf).
+1. In Visual Studio, create a C# console app (**File** > **New** > **Project** > **Visual C#** > **Console Application**) named *ThrowsNullException*. For more information about creating projects in Visual Studio, see [Walkthrough: Create a simple application](../get-started/csharp/tutorial-wpf.md).
 
 1. When the project opens in Visual Studio, open the *Program.cs* file. Replace the Main() method with the following code, which prints a line to the console and then throws a NullReferenceException:
 

docs/debugger/debugger-feature-tour.md

@@ -118,7 +118,7 @@ In most languages supported by Visual Studio, you can edit your code in the midd
 
 For more information on using the feature and on feature limitations, see [Edit and Continue](../debugger/edit-and-continue.md).
 
-To modify XAML code during a debugging session, see [Write and debug running XAML code with XAML Hot Reload](xaml-hot-reload.md).
+To modify XAML code during a debugging session, see [Write and debug running XAML code with XAML Hot Reload](../xaml-tools/xaml-hot-reload.md).
 
 ## Inspect variables with data tips
 

docs/debugger/debugger-project-settings.md

@@ -45,7 +45,7 @@ Certain project settings also affect debugging. These settings determine such th
  [Specify Symbol (.pdb) and Source Files](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md)
  Describes how the debugger uses symbol files and source files to display information for debugging.
 
- [Debug apps in Visual Studio](/visualstudio/debugger/debugging-windows-store-and-windows-universal-apps)
+ [Debug apps in Visual Studio](debugging-windows-store-and-windows-universal-apps.md)
  Describes how to debug UWP apps. (Windows Dev Center)
 
  [Debugger Settings and Preparation](../debugger/debugger-settings-and-preparation.md)

docs/debugger/debugger-tips-and-tricks.md

@@ -35,7 +35,7 @@ For more information on using the feature and on feature limitations, see [Edit
 
 ## Edit XAML code and continue debugging
 
-To modify XAML code during a debugging session, see [Write and debug running XAML code with XAML Hot Reload](xaml-hot-reload.md).
+To modify XAML code during a debugging session, see [Write and debug running XAML code with XAML Hot Reload](../xaml-tools/xaml-hot-reload.md).
 
 ## Debug issues that are hard to reproduce
 

docs/debugger/debugger-windows.md

@@ -33,7 +33,7 @@ You can open most debugger windows while you are debugging your program. To see
 |Tasks|CTR:+SHIFT+D, K|[Using the Tasks Window](../debugger/using-the-tasks-window.md)|
 |Python Debug Interactive|SHIFT+ALT+I|[Python Interactive REPL](../python/python-interactive-repl-in-visual-studio.md)|
 |JavaScript Console|CTRL+ALT+V, C|[QuickStart: Debug JavaScript](../debugger/quickstart-debug-javascript-using-the-console.md)|
-|DOM Explorer|CTRL+ALT+V, D|[Debug layout using DOM Explorer](/visualstudio/debugger/quickstart-debug-html-and-css)|
+|DOM Explorer|CTRL+ALT+V, D|[Debug layout using DOM Explorer](quickstart-debug-html-and-css.md)|
 |Live Visual Tree|-|[Inspect XAML properties while debugging](../xaml-tools/inspect-xaml-properties-while-debugging.md)|
 |Live Property Explorer|-|[Inspect XAML properties while debugging](../xaml-tools/inspect-xaml-properties-while-debugging.md)|
 |Processes|CTRL+ALT+Z|[Debug Threads and Processes](../debugger/debug-threads-and-processes.md)|

docs/debugger/debugging-and-the-hosting-process.md

@@ -24,7 +24,7 @@ The Visual Studio hosting process improves debugger performance and enables new
 > Starting in Visual Studio 2017, the option to debug using the hosting process is no longer needed and has been removed. For more information, see [Debugging: Visual Studio 2017 Aims To Speed Up Your Least Favorite Job](https://vslive.com/Blogs/News-and-Tips/2017/02/Debugging-Visual-Studio-2017-aims-to-speed-up-your-least-favorite-job.aspx).
 
 ## Partial-Trust Debugging and Click-Once Security
- Partial-trust debugging requires the hosting process. If you disable the hosting process, partial-trust debugging will not work even if partial-trust security is enabled on the **Security** page of **Project Properties**. For more information, see [How to: Debug a Partial Trust Application](/visualstudio/debugger/debugger-security).
+ Partial-trust debugging requires the hosting process. If you disable the hosting process, partial-trust debugging will not work even if partial-trust security is enabled on the **Security** page of **Project Properties**. For more information, see [How to: Debug a Partial Trust Application](debugger-security.md).
 
 ## Design-Time Expression Evaluation
  Design-time expression always uses the hosting process. Disabling the hosting process in the **Project Properties** disables design-time expression evaluation for Class Library projects. For other project types, design-time expression evaluation is not disabled. Instead, Visual Studio starts the actual executable and uses it for design-time evaluation without the hosting process. This difference could produce different results.
@@ -37,4 +37,4 @@ The Visual Studio hosting process improves debugger performance and enables new
 
 ## See also
 
-- [How to: Debug a Partial Trust Application](/visualstudio/debugger/debugger-security)
+- [How to: Debug a Partial Trust Application](debugger-security.md)

docs/debugger/debugging-applications.md

@@ -25,7 +25,7 @@ The following sections deal with debugging for specific types of applications. D
 |[Debug managed code](../debugger/debugging-managed-code.md)|Describes how to debug managed code (Visual C#, Visual Basic, F#, and C++/CLI).|
 |[Debug native code](../debugger/debugging-native-code.md)|Describes how to debug different kind of native C++ applications.|
 |[Debug GPU code](../debugger/debugging-gpu-code.md)|Describes how to debug C++ code that runs on the graphical processing unit (GPU).|
-|[Graphics diagnostics (Debugging DirectX graphics)](/visualstudio/debugger/graphics/visual-studio-graphics-diagnostics)|Describes how to debug DirectX graphics.|
+|[Graphics diagnostics (Debugging DirectX graphics)](graphics/visual-studio-graphics-diagnostics.md)|Describes how to debug DirectX graphics.|
 |[Debug ASP.NET applications](../debugger/how-to-enable-debugging-for-aspnet-applications.md)|Describes how to debug ASP.NET applications.|
 |[Debug Python code](../python/tutorial-working-with-python-in-visual-studio-step-04-debugging.md)|Describes how to debug Python code|
 |[Debug JavaScript and TypeScript applications](../javascript/debug-nodejs.md)|Describes how to debug JavaScript, TypeScript, and Node.js applications|

docs/debugger/debugging-managed-code.md

@@ -70,7 +70,7 @@ Provides considerations for debugging Windows service applications, including se
 [Debugging and Profiling](/dotnet/framework/debug-trace-profile/index)\
 Discusses debugging .NET applications and the configuration requirements.
 
-[Debugging Script and Web Applications](/visualstudio/debugger/how-to-enable-debugging-for-aspnet-applications)\
+[Debugging Script and Web Applications](how-to-enable-debugging-for-aspnet-applications.md)\
 Describes common debugging problems and techniques you may encounter when debugging script and Web applications.
 
 ## See also