Merge pull request #3597 from gewarren/redirects-second-round

Replace links to redirected topics - round 2

Author: PRMerger10

docs/code-quality/troubleshooting-code-analysis-issues.md

@@ -27,6 +27,6 @@ This topic contains troubleshooting information for the following Visual Studio
 
 ## See Also
 
-- [Analyzing Application Quality](../code-quality/analyzing-application-quality-by-using-code-analysis-tools.md)
+- [Analyzing Application Quality](../code-quality/code-analysis-for-managed-code-overview.md)
 - [Analyzing Managed Code Quality](../code-quality/code-analysis-for-managed-code-overview.md)
 - [Using Rule Sets to Group Code Analysis Rules](../code-quality/using-rule-sets-to-group-code-analysis-rules.md)

docs/cross-platform/application-lifecycle-management-alm-with-unity-apps.md

@@ -96,7 +96,7 @@ Reference link: **[Improve code quality](../test/improve-code-quality.md)**
 
 |Feature|Supported with Unity|Additional Comments|
 |-------------|--------------------------|-------------------------|
-|[Analyze managed code quality](../code-quality/analyzing-managed-code-quality-by-using-code-analysis.md)|Yes|Can analyze the C# script code within Visual Studio.|
+|[Analyze managed code quality](../code-quality/code-analysis-for-managed-code-overview.md)|Yes|Can analyze the C# script code within Visual Studio.|
 |[Find duplicate code by using code clone detection](https://msdn.microsoft.com/library/hh205279.aspx)|Yes|Can analyze the C# script code within Visual Studio.|
 |[Measure complexity and maintainability of managed code](../code-quality/code-metrics-values.md)|Yes|Can analyze the C# script code within Visual Studio.|
 |[Performance Explorer](../profiling/performance-explorer.md)|No|Use the [Unity Profiler](http://docs.unity3d.com/Manual/Profiler.html) (Unity website).|

docs/cross-platform/cross-platform-mobile-development-in-visual-studio.md

@@ -30,7 +30,7 @@ With Visual Studio Tools for Xamarin, you can target Android, iOS, and Windows i
 |[Install Visual Studio](http://visualstudio.microsoft.com/products/visual-studio-community-vs) (VisualStudio.com)|
 |[Learn about Xamarin in Visual Studio](https://visualstudio.microsoft.com/xamarin/) (VisualStudio.com)|
 |[Xamarin mobile app development documentation](/xamarin/) |
-|[DevOps with Xamarin apps](../cross-platform/application-lifecycle-management-alm-with-xamarin-apps.md) |
+|[DevOps with Xamarin apps](/xamarin/tools/ci/devops/) |
 |[Learn about Universal Windows apps in Visual Studio](https://visualstudio.microsoft.com/vs/universal-windows-platform/) (VisualStudio.com)|
 |[Learn about the similarities between Swift and C#](http://aka.ms/scposter) (download.microsoft.com)|
 

docs/extensibility/document-lock-holder-management.md

@@ -30,7 +30,7 @@ The running document table (RDT) maintains a count of open documents and any edi
 - If file "b" is open in an incompatible way, you can either let the attempted opening of file "b" by editor "A" fail, or you can let the view associated with editor "A" partially open and display an appropriate error message. The error message should instruct the user to close file "b" in the incompatible editor and then re-open file "a" using editor "A". You can also implement the [!INCLUDE[vsipsdk](../extensibility/includes/vsipsdk_md.md)] method <xref:Microsoft.VisualStudio.Shell.Interop.IVsRunningDocumentTable2.QueryCloseRunningDocument%2A> to prompt the user to close file "b" that is open in the incompatible editor. If the user closes file "b", the opening of file "a" in editor "A" continues normally.
 
 ## Additional document edit lock considerations
- You get different behavior if editor "A" is the only editor that has a document edit lock on file "b" than you would if editor "B" also holds a document edit lock on file "b". In [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)], **Class Designer** is an example of a visual designer that does not hold an edit lock on the associated code file. That is, if the user has a class diagram open in design view and the associated code file open simultaneously, and if the user modifies the code file but does not save the changes, the changes are also lost to the class diagram (.cd) file. If the **Class Designer** has the only document edit lock on the code file, the user is not asked to save the changes when closing the code file. The IDE asks the user to save the changes only after the user closes the **Class Designer**. The saved changes are reflected in both files. If both the **Class Designer** and the code file editor held document edit locks on the code file, then the user is prompted to save when closing either the code file or the form. At that point the saved changes are reflected in both the form and the code file. For more information on class diagrams, see [Work with class diagrams (Class Designer)](../ide/class-designer/working-with-class-diagrams.md).
+ You get different behavior if editor "A" is the only editor that has a document edit lock on file "b" than you would if editor "B" also holds a document edit lock on file "b". In [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)], **Class Designer** is an example of a visual designer that does not hold an edit lock on the associated code file. That is, if the user has a class diagram open in design view and the associated code file open simultaneously, and if the user modifies the code file but does not save the changes, the changes are also lost to the class diagram (.cd) file. If the **Class Designer** has the only document edit lock on the code file, the user is not asked to save the changes when closing the code file. The IDE asks the user to save the changes only after the user closes the **Class Designer**. The saved changes are reflected in both files. If both the **Class Designer** and the code file editor held document edit locks on the code file, then the user is prompted to save when closing either the code file or the form. At that point the saved changes are reflected in both the form and the code file. For more information on class diagrams, see [Work with class diagrams (Class Designer)](../ide/class-designer/designing-and-viewing-classes-and-types.md).
 
  Note that if you need to place an edit lock on a document for a non-editor, you must implement the <xref:Microsoft.VisualStudio.Shell.Interop.IVsDocumentLockHolder> interface.
 

docs/test/how-to-create-a-diagnostic-data-adapter.md

@@ -42,7 +42,7 @@ The following is a partial list of key events that you can use when you create y
 
 Use the following procedure to create diagnostic data adapter that collects a data file that is based on information that you configure when you create your test settings.
 
-For a complete example diagnostic data adapter project, including a custom configuration editor, see [Sample project for creating a diagnostic data adapter](../test/sample-project-for-creating-a-diagnostic-data-adapter.md).
+For a complete example diagnostic data adapter project, including a custom configuration editor, see [Sample project for creating a diagnostic data adapter](../test/quickstart-create-a-load-test-project.md).
 
 ##  Create and install a diagnostic data adapter
 
@@ -255,11 +255,11 @@ For a complete example diagnostic data adapter project, including a custom confi
 
      For more information about how to configure your test settings to use an environment when you run your tests, see [Collect diagnostic data in manual tests (Azure Test Plans)](/azure/devops/test/mtm/collect-more-diagnostic-data-in-manual-tests?view=vsts).
 
-     For more information about installing the configuration file, see [How to: Install a custom diagnostic data adapter](../test/how-to-install-a-custom-diagnostic-data-adapter.md)
+     For more information about installing the configuration file, see [How to: Install a custom diagnostic data adapter](../test/quickstart-create-a-load-test-project.md)
 
 12. Build your solution to create your diagnostic data adapter assembly.
 
-13. For information about installing your custom editor, see [How to: Install a custom diagnostic data adapter](../test/how-to-install-a-custom-diagnostic-data-adapter.md).
+13. For information about installing your custom editor, see [How to: Install a custom diagnostic data adapter](../test/quickstart-create-a-load-test-project.md).
 
 14. For more information about how to configure your test settings to use an environment when you run your tests, see [Collect diagnostic data in manual tests (Azure Test Plans)](/azure/devops/test/mtm/collect-more-diagnostic-data-in-manual-tests?view=vsts).
 

docs/test/unit-test-your-code.md

@@ -38,7 +38,7 @@ Use the following topics to help with understanding and creating unit tests:
 
 |Tasks|Associated Topics|
 |-|-----------------------|
-|**Quick starts and walkthroughs:** Use the following topics to learn unit testing in Visual Studio from code examples.|-   [Walkthrough: Creating and running unit tests for managed code](../test/walkthrough-creating-and-running-unit-tests-for-managed-code.md)<br />-   [Quickstart: Test-driven development with Test Explorer](../test/quick-start-test-driven-development-with-test-explorer.md)<br />-   [Add unit tests to existing C++ applications](../test/unit-testing-existing-cpp-applications-with-test-explorer.md)|
+|**Quick starts and walkthroughs:** Use the following topics to learn unit testing in Visual Studio from code examples.|-   [Walkthrough: Creating and running unit tests for managed code](../test/walkthrough-creating-and-running-unit-tests-for-managed-code.md)<br />-   [Quickstart: Test-driven development with Test Explorer](../test/quick-start-test-driven-development-with-test-explorer.md)<br />-   [Add unit tests to existing C++ applications](../test/how-to-use-microsoft-test-framework-for-cpp.md)|
 |**Unit testing with Test Explorer:** Learn how Test Explorer can help create more productive and efficient unit tests.|-   [Unit test basics](../test/unit-test-basics.md)<br />-   [Create a unit test project](../test/create-a-unit-test-project.md)<br />-   [Run unit tests with Test Explorer](../test/run-unit-tests-with-test-explorer.md)<br />-   [Install third-party unit test frameworks](../test/install-third-party-unit-test-frameworks.md)|
 |**Unit testing C++ code**|-   [Write unit tests for C/C++ with the Microsoft Unit Testing Framework for C++](../test/writing-unit-tests-for-c-cpp.md)|
 |**Isolating unit tests**|-   [Isolate code under test with Microsoft Fakes](../test/isolating-code-under-test-with-microsoft-fakes.md)|

docs/test/walkthrough-creating-and-running-unit-tests-for-windows-store-apps.md

@@ -102,5 +102,5 @@ In the **Code Editor**, edit the unit test and add the asserts and logic require
 
 ## See also
 
-- [Test UWP apps with Visual Studio](../test/create-and-run-unit-tests-for-a-store-app-in-visual-studio.md)
+- [Test UWP apps with Visual Studio](../test/unit-test-your-code.md)
 - [Build and test a UWP app](/azure/devops/pipelines/apps/windows/universal?tabs=vsts)