Merge pull request #110 from Microsoft/mikejo

ghogen · web-flow · commit dbf383536f96 · 2016-11-16T17:19:33.000-08:00
Mikejo
diff --git a/docs/debugger/configure-firewall-for-remote-debugging-dialog-box.md b/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)
diff --git a/docs/debugger/debugging-managed-code.md b/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)  
diff --git a/docs/debugger/error-firewall-no-authentication.md b/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).
diff --git a/docs/debugger/error-firewall-on-local-machine.md b/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).
diff --git a/docs/debugger/error-mixed-mode-debugging-for-ia64-processes-is-unsupported.md b/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)
diff --git a/docs/debugger/error-mixed-mode-debugging-for-x64-processes-is-supported-only-when-using-microsoft-dotnet-framework-4-or-greater.md b/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)
diff --git a/docs/debugger/error-mixed-mode-debugging-is-supported-only-when-using-microsoft-dotnet-framework-2-0-or-greater.md b/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)
diff --git a/docs/debugger/error-remote-computer-could-not-initiate-dcom-communications.md b/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)
diff --git a/docs/debugger/error-remote-machine-does-not-appear-in-a-remote-connections-dialog.md b/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)
diff --git a/docs/debugger/error-the-microsoft-visual-studio-remote-debugging-monitor-msvsmon-exe-does-not-appear-to-be-running-on-the-remote-computer.md b/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.  
diff --git a/docs/debugger/error-the-visual-studio-remote-debugger-service-on-the-target-computer-cannot-connect-back-to-this-computer.md b/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.  
   
diff --git a/docs/debugger/error-unable-to-connect-to-the-machine-name-the-machine-cannot-be-found-on-the-network.md b/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)
diff --git a/docs/debugger/error-unable-to-initiate-dcom-communication.md b/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.  
   
diff --git a/docs/debugger/how-can-i-use-debugger-windows-while-debugging-a-foreground-program-q.md b/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)   
diff --git a/docs/debugger/introducing-spy-increment.md b/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.  
   
diff --git a/docs/debugger/message-options-dialog-box.md b/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)  
diff --git a/docs/debugger/message-properties-dialog-box.md b/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)  
diff --git a/docs/debugger/message-search-dialog-box.md b/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)  
diff --git a/docs/debugger/messages-view.md b/docs/debugger/messages-view.md
@@ -64,7 +64,7 @@ Spy++ Messages View
  [Controlling Messages View](../debugger/how-to-control-messages-view.md)  
  Explains how to manage 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.  
   
  [Searching for a Message in Messages View](../debugger/how-to-search-for-a-message-in-messages-view.md)  
diff --git a/docs/debugger/prerequistes-for-remote-debugging-web-applications.md b/docs/debugger/prerequistes-for-remote-debugging-web-applications.md
@@ -40,7 +40,7 @@ translation.priority.ht:
 # Prerequistes for Remote Debugging Web Applications
 With the [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] debugger, you can debug a Web application transparently on the local computer or a remote server. This means that the debugger functions the same way and allows you to use the same features on either computer. For remote debugging to work correctly, however, there are some prerequisites.  
   
--   [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] remote debugging components must be installed on the server you want to debug. For more information, see [Setting Up Remote Debugging](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md).  
+-   [!INCLUDE[vsprvs](../code-quality/includes/vsprvs_md.md)] remote debugging components must be installed on the server you want to debug. For more information, see [Remote Debugging](../debugger/remote-debugging.md).  
   
 -   By default, the [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] worker process runs as an ASPNET user process. As a result, you must have Administrator privileges on the computer where [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] runs to debug it. The name of the [!INCLUDE[vstecasp](../code-quality/includes/vstecasp_md.md)] worker process varies by debug scenario and version of IIS. For more information, see [How to: Find the Name of the ASP.NET Process](../debugger/how-to-find-the-name-of-the-aspnet-process.md).  
   
diff --git a/docs/profiling/adding-tier-interaction-data-from-the-command-line.md b/docs/profiling/adding-tier-interaction-data-from-the-command-line.md
@@ -45,7 +45,7 @@ Tier interaction profiling provides additional information about the execution t
   
  **Collecting TIP data on a remote machine**  
   
- To collect tier interaction data on a remote machine, you must copy the **vs_profiler_***\<Platform>***_***\<Language>***.exe** file from the *%VSInstallDir%***\Team Tools\Performance Tools\Setups** folder of a Visual Studio machine to the remote computer and install it. You cannot use the profiling tools in the [Visual Studio Remote Tools](../Topic/Set%20Up%20the%20Remote%20Tools%20on%20the%20Device.md) download package.  
+ To collect tier interaction data on a remote machine, you must copy the **vs_profiler_***\<Platform>***_***\<Language>***.exe** file from the *%VSInstallDir%***\Team Tools\Performance Tools\Setups** folder of a Visual Studio machine to the remote computer and install it. You cannot use the profiling tools in the [Remote Debugging](../debugger/remote-debugging.md) download package.  
   
  **TIP reports**  
   
diff --git a/docs/profiling/beginners-guide-to-performance-profiling.md b/docs/profiling/beginners-guide-to-performance-profiling.md
@@ -48,37 +48,37 @@ In this topic, we'll discuss analyzing CPU usage in your normal debugging workfl
   
 1.  Open the project you want to debug in Visual Studio and set a breakpoint in your app at the point where you want to examine CPU usage.
 
-2.  Set a second breakpoint at the end of the function or regiion of code that you want to analyze.
+2.  Set a second breakpoint at the end of the function or region of code that you want to analyze.
   
-2.  The **Diagnostic Tools** window appears automatically unless you have turned it off. To bring up the window again, click **Debug / Windows / Show Diagnostic Tools**.
+3.  The **Diagnostic Tools** window appears automatically unless you have turned it off. To bring up the window again, click **Debug / Windows / Show Diagnostic Tools**.
 
-3.  You can choose whether to see **CPU Usage**, [Memory Usage](../profiling/Memory-Usage.md), or both, with the **Select Tools** setting on the toolbar. If you are running Visual Studio Enterprise,  you can also enable or disable IntelliTrace in **Tools / Options / IntelliTrace**.
+4.  You can choose whether to see **CPU Usage**, [Memory Usage](../profiling/Memory-Usage.md), or both, with the **Select Tools** setting on the toolbar. If you are running Visual Studio Enterprise,  you can also enable or disable IntelliTrace in **Tools / Options / IntelliTrace**.
 
      ![Show Diagnostics Tools](../profiling/media/DiagToolsSelectTool.png "DiagToolsSelectTool")
 
      We will mainly be looking at CPU utilization, so make sure that **CPU Usage** is enabled (it is enabled by default).
 
-4.  Click **Debug / Start Debugging** (or **Start** on the toolbar, or **F5**).
+5.  Click **Debug / Start Debugging** (or **Start** on the toolbar, or **F5**).
 
      When the app finishes loading, the Summary view of the Diagnostics Tools appears.
 
      ![Diagnostics Tools Summary Tab](../profiling/media/DiagToolsSummaryTab.png "DiagToolsSummaryTab")
 
      For more information on the events, see [Searching and filtering the Events tab of the Diagnostic Tools window](http://blogs.msdn.com/b/visualstudioalm/archive/2015/11/12/searching-and-filtering-the-events-tab-of-the-diagnostic-tools-window.aspx)
 
-5.  Run the scenario that will cause your first breakpoint to be hit.
+6.  Run the scenario that will cause your first breakpoint to be hit.
 
-6.  While the debugger is paused, enable the collection of the CPU Usage data and then open the **CPU Usage** tab.
+7.  While the debugger is paused, enable the collection of the CPU Usage data and then open the **CPU Usage** tab.
 
      ![Diagnostics Tools Enable CPU Profiling](../profiling/media/DiagToolsEnableCPUProfiling.png "DiagToolsEnableCPUProfiling")
 
-     When you choose **Enable CPU Profiling**, Visual Studio will begin recording your functions and how much time they take to execute. You can only view this collected data when your application is halted at a breakpoint.eX0000.
+     When you choose **Enable CPU Profiling**, Visual Studio will begin recording your functions and how much time they take to execute. You can only view this collected data when your application is halted at a breakpoint.
 
-7.  Hit F5 to run the app to your second breakpoint.
+8.  Hit F5 to run the app to your second breakpoint.
 
      Now, you now have performance data for your application specifically for the region of code that runs between the two breakpoints.
 
-7.  Select the region you're interested in analyzing in the CPU timeline (it must be a region that shows profiling data).
+9.  Select the region you're interested in analyzing in the CPU timeline (it must be a region that shows profiling data).
 
      ![Diagnostics Tools Selecting a Time Segment](../profiling/media/DiagToolsSelectTimeSegment.png "DiagToolsSelectTimeSegment")
 
diff --git a/docs/profiling/how-to-profile-javascript-code-in-web-pages.md b/docs/profiling/how-to-profile-javascript-code-in-web-pages.md
@@ -43,11 +43,7 @@ translation.priority.mt:
 -   Internet Explorer 8 or later.  
   
 > [!WARNING]
->  To profile JavaScript in Windows Store apps, see one of the following topics:  
->   
->  -   [JavaScript Function Timing](../Topic/JavaScript%20Function%20Timing.md) [JavaScript Function Timing on a Remote Device](../Topic/JavaScript%20Function%20Timing%20on%20a%20Remote%20Device.md)  
-> -   [Analyze JavaScript Function Timing data](../Topic/Analyze%20JavaScript%20Function%20Timing%20data.md)  
-> -  
+>  To profile JavaScript in Windows Store apps, see [JavaScript Memory](../profiling/javascript-memory.md) 
   
  You can use the Profiling Wizard to create a performance session. Specify the instrumentation method and then specify the JavaScript profiling option on the Instrumentation page of the properties dialog box for the performance session.  
   
diff --git a/docs/profiling/html-ui-responsiveness.md b/docs/profiling/html-ui-responsiveness.md
diff --git a/docs/profiling/performance-tools-on-windows-8-and-windows-server-2012-applications.md b/docs/profiling/performance-tools-on-windows-8-and-windows-server-2012-applications.md
