Merge pull request #111 from Microsoft/master

Merge link and breadcrumb fixes into live

Author: ghogen

docs/_breadcrumb/toc.yml

@@ -4,82 +4,86 @@
   items:
   - name: Visual Studio
     tocHref: /visualstudio/
-    topicHref: /visualstudio/welcome-to-visual-studio
+    topicHref: /visualstudio
     items:
-    - name: Cross Platform
-      tocHref: /visualstudio/cross-platform/
-      topicHref: /visualstudio/cross-platform/cross-platform-mobile-development-in-visual-studio
-    - name: Data Tools
-      tocHref: /visualstudio/data-tools/ 
-      topicHref: /visualstudio/data-tools/accessing-data-in-visual-studio
-    - name: Extensibility
-      tocHref: /visualstudio/extensibility/
-      topicHref: /visualstudio/extensibility/extensibility-in-visual-studio
+    - name: Documentation
+      tocHref: /visualstudio/
+      topicHref: /visualstudio/welcome-to-visual-studio
       items:
-      - name: Inside the Visual Studio SDK
-        tocHref: /visualstudio/extensibility/internals/
-        topicHref: /visualstudio/extensibility/internals/inside-the-visual-studio-sdk
-      - name: Debugger Extensibility
-        tocHref: /visualstudio/extensibility/debugger/
-        topicHref: /visualstudio/extensibility/debugger/visual-studio-debugger-extensibility
-      - name: User Experience Guidelines
-        tocHref: /visualstudio/extensibility/ux-guidelines/
-        topicHref: /visualstudio/extensibility/visual-studio-user-experience-guidelines
-    - name: IDE 
-      tocHref: /visualstudio/ide/
-      topicHref: /visualstudio/ide/index
-      items:
-      - name: Deployment
-        tocHref: /visualstudio/deployment/
-        topicHref: /visualstudio/deployment/deploying-applications-services-and-components
-      - name: Designers
-        tocHref: /visualstudio/designers/
-        topicHref: /visualstudio/designers/designing-user-interfaces
-      - name: CSharp IDE
-        tocHref: /visualstudio/csharp-ide/
-        topicHref: /visualstudio/csharp-ide/using-the-visual-studio-development-environment-for-csharp
-      - name: Code Quality
-        tocHref: /visualstudio/code-quality/
-        topicHref: /visualstudio/code-quality/analyzing-application-quality-by-using-code-analysis-tools
-      - name: Modeling Architecture
-        tocHref: /visualstudio/modeling/
-        topicHref: /visualstudio/modeling/analyze-and-model-your-architecture
-      - name: Debugging
-        tocHref: /visualstudio/debugger/ 
-        topicHref: /visualstudio/debugger/debugging-in-visual-studio
+      - name: Cross Platform
+        tocHref: /visualstudio/cross-platform/
+        topicHref: /visualstudio/cross-platform/cross-platform-mobile-development-in-visual-studio
+      - name: Data Tools
+        tocHref: /visualstudio/data-tools/ 
+        topicHref: /visualstudio/data-tools/accessing-data-in-visual-studio
+      - name: Extensibility
+        tocHref: /visualstudio/extensibility/
+        topicHref: /visualstudio/extensibility/extensibility-in-visual-studio
         items:
-        - name: DIA SDK
-          tocHref: /visualstudio/debugger/debug-interface-access/
-          topicHref: /visualstudio/debugger/debug-interface-access/debug-interface-access-sdk
-      - name: Profiling
-        tocHref: /visualstudio/profiling/
-        topicHref: /visualstudio/profiling/profiling-tools
-      - name: Testing
-        tocHref: /visualstudio/test/
-        topicHref: /visualstudio/test/improve-code-quality
-      - name: Workflow Designer
-        tocHref: /visualstudio/workflow-designer/
-        topicHref: /visualstudio/workflow-designer/developing-applications-with-the-workflow-designer
-      - name: Reference
-        tocHref: /visualstudio/ide/reference/
-        topicHref: /visualstudio/ide/reference/visual-studio-reference
+        - name: Inside the Visual Studio SDK
+          tocHref: /visualstudio/extensibility/internals/
+          topicHref: /visualstudio/extensibility/internals/inside-the-visual-studio-sdk
+        - name: Debugger Extensibility
+          tocHref: /visualstudio/extensibility/debugger/
+          topicHref: /visualstudio/extensibility/debugger/visual-studio-debugger-extensibility
+        - name: User Experience Guidelines
+          tocHref: /visualstudio/extensibility/ux-guidelines/
+          topicHref: /visualstudio/extensibility/visual-studio-user-experience-guidelines
+      - name: IDE 
+        tocHref: /visualstudio/ide/
+        topicHref: /visualstudio/ide/index
         items:
-        - name: XML Tools
-          tocHref: /visualstudio/xml-tools/
-          topicHref: /visualstudio/xml-tools/xml-tools-in-visual-studio
-        - name: MSBuild
-          tocHref: /visualstudio/msbuild/
-          topicHref: /visualstudio/msbuild/msbuild1
-    - name: Installation
-      tocHref: /visualstudio/install/
-      topicHref: /visualstudio/install/install-visual-studio-2015
-    - name: JavaScript
-      tocHref: /visualstudio/javascript/
-      topicHref: /visualstudio/javascript/javascript-in-visual-studio
-    - name: Porting
-      tocHref: /visualstudio/porting/
-      topicHref: /visualstudio/porting/porting-migrating-and-upgrading-visual-studio-projects
-    - name: Python
-      tocHref: /visualstudio/python/
-      topicHref: /visualstudio/python/getting-started-with-python
+        - name: Deployment
+          tocHref: /visualstudio/deployment/
+          topicHref: /visualstudio/deployment/deploying-applications-services-and-components
+        - name: Designers
+          tocHref: /visualstudio/designers/
+          topicHref: /visualstudio/designers/designing-user-interfaces
+        - name: CSharp IDE
+          tocHref: /visualstudio/csharp-ide/
+          topicHref: /visualstudio/csharp-ide/using-the-visual-studio-development-environment-for-csharp
+        - name: Code Quality
+          tocHref: /visualstudio/code-quality/
+          topicHref: /visualstudio/code-quality/analyzing-application-quality-by-using-code-analysis-tools
+        - name: Modeling Architecture
+          tocHref: /visualstudio/modeling/
+          topicHref: /visualstudio/modeling/analyze-and-model-your-architecture
+        - name: Debugging
+          tocHref: /visualstudio/debugger/ 
+          topicHref: /visualstudio/debugger/debugging-in-visual-studio
+          items:
+          - name: DIA SDK
+            tocHref: /visualstudio/debugger/debug-interface-access/
+            topicHref: /visualstudio/debugger/debug-interface-access/debug-interface-access-sdk
+          - name: Profiling
+            tocHref: /visualstudio/profiling/
+            topicHref: /visualstudio/profiling/profiling-tools
+        - name: Testing
+          tocHref: /visualstudio/test/
+          topicHref: /visualstudio/test/improve-code-quality
+        - name: Workflow Designer
+          tocHref: /visualstudio/workflow-designer/
+          topicHref: /visualstudio/workflow-designer/developing-applications-with-the-workflow-designer
+        - name: Reference
+          tocHref: /visualstudio/ide/reference/
+          topicHref: /visualstudio/ide/reference/visual-studio-reference
+          items:
+          - name: XML Tools
+            tocHref: /visualstudio/xml-tools/
+            topicHref: /visualstudio/xml-tools/xml-tools-in-visual-studio
+          - name: MSBuild
+            tocHref: /visualstudio/msbuild/
+            topicHref: /visualstudio/msbuild/msbuild1
+      - name: Installation
+        tocHref: /visualstudio/install/
+        topicHref: /visualstudio/install/install-visual-studio-2015
+      - name: JavaScript
+        tocHref: /visualstudio/javascript/
+        topicHref: /visualstudio/javascript/javascript-in-visual-studio
+      - name: Port, Migrate, Upgrade
+        tocHref: /visualstudio/porting/
+        topicHref: /visualstudio/porting/port-migrate-and-upgrade-visual-studio-projects
+      - name: Python
+        tocHref: /visualstudio/python/
+        topicHref: /visualstudio/python/getting-started-with-python
 

docs/debugger/configure-firewall-for-remote-debugging-dialog-box.md

@@ -59,5 +59,5 @@ This dialog box appears when the Windows Firewall blocks the debugger from recei
 
 ## See Also  
  [Debugger Security](../debugger/debugger-security.md)   
- [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md)   
+ [Remote Debugging](../debugger/remote-debugging.md)
  [Debugging User Interface Reference](../debugger/debugging-user-interface-reference.md)

docs/debugger/debugging-managed-code.md

@@ -93,7 +93,7 @@ This section covers common debugging problems and techniques for managed applica
  [Debugging Script and Web Applications](../debugger/debugging-web-applications-and-script.md)  
  Describes common debugging problems and techniques you may encounter when debugging script and Web applications.  
 
- [What’s New for the Debugger in Visual Studio 2015](../debugger/what’s-new-for-the-debugger-in-visual-studio-2015.md)  
+ [What’s New for the Debugger in Visual Studio 2015](../debugger/what-s-new-for-the-debugger-in-visual-studio.md)  
  Description of new debugging features added in this release of [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)].  
 
  [Debugging Home Page](../debugger/debugging-in-visual-studio.md)  

docs/debugger/error-firewall-no-authentication.md

@@ -41,4 +41,4 @@ The Internet Connection Firewall on the remote machine is not set up to allow re
 > [!NOTE]
 >  The remote debugger is able to automatically configure the Windows Firewall. When using a firewall other than the Windows Firewall such as third party software firewall or a hardware firewall, the firewall must be manually configured to allow remote debugging. To do so, allow traffic on TCP/IP ports that msvsmon.exe is listening on. By default, these are port 4018 and 4019, where 4018 is used on all Operating Systems, and 4019 is used only on Windows x64 to allow debugging x86 processes.  
   
- For more information, see [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md).
+ For more information, see [Remote Debugging](../debugger/remote-debugging.md).

docs/debugger/error-firewall-on-local-machine.md

@@ -38,4 +38,4 @@ translation.priority.ht:
 # Error: Firewall on Local Machine
 The Internet Connection Firewall on the local machine, the machine you are running Visual Studio from, is not set up to allow remote debugging. For managed or native remote debugging with the default transport, the TCP 135 port must be opened for DCOM traffic. File and printer sharing must be opened, and devenv.exe must be added to the exceptions list. Opening some IPSEC ports may be necessary as well.  
 
- For more information, see [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md).
+ For more information, see [Remote Debugging](../debugger/remote-debugging.md).

docs/debugger/error-mixed-mode-debugging-for-ia64-processes-is-unsupported.md

@@ -43,4 +43,4 @@ The [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] debugger does not
 -   Build a 32-bit version of your application for debugging.  
 
 ## See Also  
- [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md)
+ [Remote Debugging](../debugger/remote-debugging.md)

docs/debugger/error-mixed-mode-debugging-for-x64-processes-is-supported-only-when-using-microsoft-dotnet-framework-4-or-greater.md

@@ -47,4 +47,4 @@ To debug mixed native and managed code in a 64-bit process, you must have [!INCL
     -   Build a 32-bit version of your application for debugging.  
 
 ## See Also  
- [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md)
+ [Remote Debugging](../debugger/remote-debugging.md)

docs/debugger/error-mixed-mode-debugging-is-supported-only-when-using-microsoft-dotnet-framework-2-0-or-greater.md

@@ -43,4 +43,4 @@ To debug mixed native and managed code, you must have [!INCLUDE[dnprdnshort](../
 -   Upgrade the [!INCLUDE[dnprdnshort](../code-quality/includes/dnprdnshort_md.md)] to version 2.0, 3.0, 3.5, or 4.0.  
 
 ## See Also  
- [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md)
+ [Remote Debugging](../debugger/remote-debugging.md)

docs/debugger/error-remote-computer-could-not-initiate-dcom-communications.md

@@ -46,11 +46,11 @@ A DCOM error occurred when the remote machine tried to communicate with the loca
 
 ### To correct this error  
 
-1.  If the local machine has Windows Firewall enabled, see [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md) for instructions about how to configure the firewall for local debugging.  
+1.  If the local machine has Windows Firewall enabled, see [Remote Debugging](../debugger/remote-debugging.md) for instructions about how to configure the firewall for local debugging.  
 
 2.  Test Windows authentication by trying to open a file share on the local machine from the remote server.  
 
 3.  To restore Windows authentication, try rebooting both machines. Examine event logs on local and remote machines for Kerberos errors and contact domain administrators for known problems.  
 
 ## See Also  
- [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md)
+ [Remote Debugging](../debugger/remote-debugging.md)

docs/debugger/error-remote-machine-does-not-appear-in-a-remote-connections-dialog.md

@@ -50,4 +50,4 @@ If the remote machine does not appear in the Remote Connections dialog, check th
 -   Antivirus software is blocking communication between Visual Studio and the remote machine. To fix this, configure antivirus software to allow Visual Studio and the remote debugger (msvsmon) to communicate.  
 
 ## See Also  
- [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md)
+ [Remote Debugging](../debugger/remote-debugging.md)

docs/debugger/error-the-microsoft-visual-studio-remote-debugging-monitor-msvsmon-exe-does-not-appear-to-be-running-on-the-remote-computer.md

@@ -37,7 +37,7 @@ translation.priority.mt:
   - "tr-tr"
 ---
 # Error: The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.
-This error message means that Visual Studio could not find the correct instance of the Visual Studio Remote Debugging Monitor on the remote computer. The Visual Studio Remote Debugging Monitor must be installed for remote debugging to work. For information about downloading and setting up the remote debugger, see [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md).  
+This error message means that Visual Studio could not find the correct instance of the Visual Studio Remote Debugging Monitor on the remote computer. The Visual Studio Remote Debugging Monitor must be installed for remote debugging to work. For information about downloading and setting up the remote debugger, see [Remote Debugging](../debugger/remote-debugging.md).  
 
 > [!IMPORTANT]
 >  If you believe you have received this message because of a product bug, please report this issue to Visual Studio [Send a Smile](../Topic/Visual%20Studio%20Send%20a%20Smile%20Instructions.md). If you need more help, see [Talk to Us](../ide/talk-to-us.md) for ways to contact Microsoft.  

docs/debugger/error-the-visual-studio-remote-debugger-service-on-the-target-computer-cannot-connect-back-to-this-computer.md

@@ -58,7 +58,7 @@ This error means that the Visual Studio Remote Debugger service is running under
 
 ### To correct this error  
 
-1.  Make sure the Visual Studio Remote Debugger service is correctly set up on the remote computer. For more information, see [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md).  
+1.  Make sure the Visual Studio Remote Debugger service is correctly set up on the remote computer. For more information, see [Remote Debugging](../debugger/remote-debugging.md).  
 
 2.  Run the remote debugger service under an account that can access the debugger host computer, as shown in the previous table.  
 

docs/debugger/error-unable-to-connect-to-the-machine-name-the-machine-cannot-be-found-on-the-network.md

@@ -59,5 +59,5 @@ This behavior occurs if one of the following conditions is true:
 -   Make sure that the password that you are using to connect to the remote computer is valid and has not expired.  
 
 ## See Also  
- [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md)   
+ [Remote Debugging](../debugger/remote-debugging.md)   
  [Debugger Settings and Preparation](../debugger/debugger-settings-and-preparation.md)

docs/debugger/error-unable-to-initiate-dcom-communication.md

@@ -40,7 +40,7 @@ A DCOM error occurred when the local machine tried to communicate with the remot
 
 ### To correct this error  
 
--   If the remote machine has Windows Firewall enabled, see [Set Up the Remote Tools on the Device](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md) for instructions about how to configure the firewall for local debugging.  
+-   If the remote machine has Windows Firewall enabled, see [Remote Debugging](../debugger/remote-debugging.md) for instructions about how to configure the firewall for local debugging.  
 
 -   To restore Windows authentication, try rebooting both machines. Examine event logs on local and remote machines for Kerberos errors and contact domain administrators for known problems.  
 

docs/debugger/how-can-i-use-debugger-windows-while-debugging-a-foreground-program-q.md

@@ -47,7 +47,7 @@ translation.priority.ht:
  I am trying to debug a screen-painting problem. To observe this problem, I have to keep my program in the foreground, which means I do not have access to the debugging windows. What can I do?  
 
 ## Solution  
- If you have a second computer, you can use remote debugging. With a two-computer setup, you can watch the screen painting on the remote computer while you operate the debugger on the host. For more information on remote debugging, see [Setting Up Remote Debugging](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md).  
+ If you have a second computer, you can use remote debugging. With a two-computer setup, you can watch the screen painting on the remote computer while you operate the debugger on the host. For more information on remote debugging, see [Remote Debugging](../debugger/remote-debugging.md).  
 
 ## See Also  
  [Debugging Native Code FAQs](../debugger/debugging-native-code-faqs.md)   

docs/debugger/introducing-spy-increment.md

@@ -44,7 +44,7 @@ Spy++ lets you perform the following tasks:
 
 -   Use the [Finder Tool](../debugger/how-to-use-the-finder-tool.md) to select a window by mouse pointer positioning.  
 
--   Set [message options](_asug_choosing_message_options) by using complex message log selection parameters.  
+-   Set [message option](../debugger/how-to-open-messages-view-from-find-window.md) by using complex message log selection parameters.  
 
  Spy++ has a toolbar and hyperlinks to help you work faster. It also provides a **Refresh** command to update the active view, a **Window Finder Tool** to make spying easier, and a **Font** dialog box to customize view windows. Additionally, Spy++ lets you save and restore user preferences.  
 

docs/debugger/message-options-dialog-box.md

@@ -57,7 +57,7 @@ Use this dialog box to select which messages are listed in [Messages View](../de
  [Searching for a Message in Messages View](../debugger/how-to-search-for-a-message-in-messages-view.md)  
  Explains how to find a specific message in Messages view.  
 
- [Opening Messages View from Find Window](_asug_choosing_message_options)  
+ [Opening Messages View from Find Window](../debugger/how-to-open-messages-view-from-find-window.md)  
  Explains how to open Messages view from the Find Window dialog box.  
 
  [Messages View](../debugger/messages-view.md)  

docs/debugger/message-properties-dialog-box.md

@@ -64,7 +64,7 @@ Use this dialog box to find out more about a specific message. To display this d
  [Spy++ Reference](../debugger/spy-increment-reference.md)  
  Includes sections describing each Spy++ menu and dialog box.  
 
- [Opening Messages View from Find Window](_asug_choosing_message_options)  
+ [Opening Messages View from Find Window](../debugger/how-to-open-messages-view-from-find-window.md)  
  Explains how to open Messages view from the Find Window dialog box.  
 
  [Searching for a Message in Messages View](../debugger/how-to-search-for-a-message-in-messages-view.md)  

docs/debugger/message-search-dialog-box.md

@@ -57,7 +57,7 @@ Use this dialog box to find and select the node for a specific message in [Messa
  [Searching for a Message in Messages View](../debugger/how-to-search-for-a-message-in-messages-view.md)  
  Explains how to find a specific message in Messages view.  
 
- [Opening Messages View from Find Window](_asug_choosing_message_options)  
+ [Opening Messages View from Find Window](../debugger/how-to-open-messages-view-from-find-window.md)  
  Explains how to open Messages view from the Find Window dialog box.  
 
  [Messages View](../debugger/messages-view.md)