Merge branch 'master' into master

Author: timsneath

docs/debugger/TOC.md

@@ -1,5 +1,5 @@
 ---
-title: "Inspect Variables in the Debugger in Visual Studio | Microsoft Docs"
+title: "Inspect Variables in the Autos and Locals Windows | Microsoft Docs"
 ms.custom: "H1Hack27Feb2017"
 ms.date: "04/17/2017"
 ms.reviewer: ""

docs/debugger/autos-and-locals-windows.md

@@ -57,13 +57,13 @@ This topic describes how to configure the firewall to enable remote debugging on
 |||||  
 |-|-|-|-|  
 |**Ports**|**Incoming/Outgoing**|**Protocol**|**Description**|   
-|4022|Incoming|TCP|For VS 2017. The port number is incremented by 2 for each Visual Studio version. For more information, see [Visual Studio Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments).|  
-|4023|Incoming|TCP|For VS 2017. The port number is incremented by 2 for each Visual Studio version. (Only used to remote debug a 32-bit process from the 64-bit version of the remote debugger.) For more information, see  [Visual Studio Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments).| 
+|4022|Incoming|TCP|For VS 2017. The port number is incremented by 2 for each Visual Studio version. For more information, see [Visual Studio Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments.md).|  
+|4023|Incoming|TCP|For VS 2017. The port number is incremented by 2 for each Visual Studio version. (Only used to remote debug a 32-bit process from the 64-bit version of the remote debugger.) For more information, see  [Visual Studio Remote Debugger Port Assignments](../debugger/remote-debugger-port-assignments.md).| 
 |3702|Outgoing|UDP|(Optional) Required for remote debugger discovery.|    
 
 ## How to Configure Ports in Windows Firewall  
 
-When you install Visual Studio or the remote debugger, the software will try to open the correct ports. However, in some scenarios, you may need to open a port manually. (To verify that ports are open, see [Troubleshooting](#troubleshooting).) Some instructions may be different on older versions of Windows.
+When you install Visual Studio or the remote debugger, the software will try to open the correct ports. However, in some scenarios (such as using a third party firewall), you may need to open a port manually. If you need to verify that ports are open, see [Troubleshooting](#troubleshooting). Some instructions for opening a port may be different on older versions of Windows.
 
 To open a port:
 
@@ -86,9 +86,9 @@ To open a port:
 
 ## <a name="troubleshooting"></a>Troubleshooting
 
-When you install Visual Studio or the remote debugger, the software will try to open the correct ports. In some scenarios, you may need to verify that the correct ports are open.
+If you are having trouble attaching to your app with the remote debugger, you may need to verify that the correct ports are open.
 
-### Verify that the Windows Firewall is configured correctly on the Visual Studio Computer  
+### Verify that ports are open in the Windows Firewall on the Visual Studio Computer  
  The instructions for configuring the Windows firewall differ slightly on different operating systems. On Windows 8/8.1, Windows 10, and Windows Server 2012, the word **app** is used; on Windows 7 or Windows Server 2008, the word **program** is used;  In the following steps we will use the word **app**.  
 
 1.  Open the Windows Firewall page. (In the **Start** menu search box, type **Windows Firewall**).  
@@ -101,7 +101,7 @@ When you install Visual Studio or the remote debugger, the software will try to
 
 5.  In the **Allowed apps and features** list, select **Visual Studio Remote Debugger**. Check one or more network types (**Domain, Home/Work (Private), Public**) that you want the remote debugging monitor to communicate with. The types must include the network to which the Visual Studio computer is connected. 
 
-### Verify that the Windows Firewall is configured correctly on the remote computer  
+### Verify that ports are open in the Windows Firewall on the remote computer  
  The remote debugging components can be installed on the remote computer or run from a shared directory. The firewall of the remote computer must be configured in both cases. The remote debugging components are located in:  
 
  **\<Visual Studio installation directory>\Common7\IDE\Remote Debugger**  

docs/debugger/configure-the-windows-firewall-for-remote-debugging.md

@@ -1,5 +1,5 @@
 ---
-title: "Get started debugging an installed app package (UWP) | Microsoft Docs"
+title: "Debug an installed app package (UWP) | Microsoft Docs"
 ms.custom: "H1Hack27Feb2017"
 ms.date: "12/09/2016"
 ms.reviewer: ""
@@ -40,7 +40,7 @@ translation.priority.mt:
   - "pt-br"
   - "tr-tr"
 ---
-# Get started debugging an installed app package in Visual Studio (UWP)
+# Debug an installed app package in Visual Studio (UWP)
 
 You can debug any installed app package by selecting **Debug**, **Other Debug Targets**, and then **Debug Installed App Package**. This debugging method is available for Universal Windows Apps (UWP) on these devices:
 

docs/debugger/debug-installed-app-package.md

@@ -1,7 +1,7 @@
 ---
 title: "Debugger Feature Tour | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/04/2017"
+ms.custom: "H1HackMay2017"
+ms.date: "05/19/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -31,7 +31,7 @@ translation.priority.mt:
   - "pt-br"
   - "tr-tr"
 ---
-# Debugger feature tour
+# Feature Tour of the Visual Studio Debugger
 
 This topic introduces the features of the Visual Studio debugger. If you want to follow along by opening your own app in Visual Studio, you can do that, or you can follow along with a sample app using the [step-by-step Beginner's Guide](../debugger/getting-started-with-the-debugger.md).
 

docs/debugger/debugger-feature-tour.md

@@ -1,5 +1,5 @@
 ---
-title: "Debugging Basics: Registers Window | Microsoft Docs"
+title: "About the Registers window | Microsoft Docs"
 ms.custom: ""
 ms.date: "11/04/2016"
 ms.reviewer: ""
@@ -37,7 +37,7 @@ translation.priority.ht:
   - "zh-cn"
   - "zh-tw"
 ---
-# Debugging Basics: Registers Window
+# About the Registers Window in Visual Studio
 The **Registers** window is available only if address-level debugging is enabled in the **Options** dialog box, **Debugging** node.  
 
  Registers are special locations within a processor (CPU) that are used to store small pieces of data that the processor is actively working on. Compiling or interpreting source code generates instructions that move data from memory into the registers and back again, as needed. Accessing data in registers is very fast compared to accessing data in memory, so code that allows the processor to keep data in a register and access it repeatedly tends to execute faster than code that requires the processor to constantly load and unload registers. To make it easier for the compiler to keep data in registers, and perform other optimizations, you should avoid using global variables and rely on local variables as much as possible. Code written in this fashion is said to have good locality of reference. In some languages, such as C/C++, the programmer can declare a register variable, which tells the compiler to try its best to keep the variable in a register at all times. For more information, see [Register Keyword](http://msdn.microsoft.com/en-us/5b66905a-2f7f-4918-bb55-5e66d4bc50f9).  

docs/debugger/debugging-basics-registers-window.md

@@ -1,7 +1,7 @@
 ---
 title: "Get started debugging multithreaded applications | Microsoft Docs"
-ms.custom: ""
-ms.date: "04/25/2017"
+ms.custom: "H1HackMay2017"
+ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 

docs/debugger/get-started-debugging-multithreaded-apps.md

@@ -1,7 +1,7 @@
 ---
 title: "Get started with the debugger | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/04/2017"
+ms.custom: "H1HackMay2017"
+ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -31,7 +31,7 @@ translation.priority.mt:
   - "pt-br"
   - "tr-tr"
 ---
-# Get started with the debugger
+# Get started with the Visual Studio debugger
 
 This topic introduces the features of the Visual Studio debugger in an step-by-step walkthrough. If you want a higher-level view of the debugger features, see [Debugger Feature Tour](../debugger/debugger-feature-tour.md).
 

docs/debugger/getting-started-with-the-debugger.md

@@ -1,6 +1,6 @@
 ---
-title: "How to: Enable Debugging for ASP.NET Applications | Microsoft Docs"
-ms.custom: ""
+title: "Enable Debugging for ASP.NET Applications | Microsoft Docs"
+ms.custom: "H1HackMay2017"
 ms.date: "04/04/17"
 ms.reviewer: ""
 ms.suite: ""
@@ -37,7 +37,7 @@ translation.priority.ht:
   - "zh-cn"
   - "zh-tw"
 ---
-# How to: Enable Debugging for ASP.NET Applications
+# Enable Debugging for ASP.NET Applications in Visual Studio
 To enable debugging, you must enable it in the application's web.config file and in the project properties. 
 
 > [!NOTE]  

docs/debugger/how-to-enable-debugging-for-aspnet-applications.md

@@ -1,5 +1,5 @@
 ---
-title: "View the call stack in the debugger in Visual Studio | Microsoft Docs"
+title: "View the call stack in the Visual Studio debugger | Microsoft Docs"
 ms.custom: "H1Hack27Feb2017"
 ms.date: "04/06/2017"
 ms.reviewer: ""
@@ -48,7 +48,7 @@ translation.priority.ht:
   - "zh-cn"
   - "zh-tw"
 ---
-# Use the call stack in the Visual Studio debugger
+# View the call stack and use the Call Stack Window in the Visual Studio debugger
 
 By using the **Call Stack** window, you can view the function or procedure calls that are currently on the stack. The **Call Stack** window shows the order in which methods and functions are getting called. The call stack is a good way to examine and understand the execution flow of an app.
 

docs/debugger/how-to-use-the-call-stack-window.md

@@ -71,9 +71,7 @@ This feature is available only if address-level debugging is enabled the **Optio
   
 ### To display the Disassembly window  
 
--   On the **Debug** menu, choose **Windows**, and click **Disassembly**.  
-  
-     The debugger must be running or in break mode.  
+-   While you are debugging, select **Debug / Windows** and then click **Disassembly**.
 
 ### To turn optional information on or off  
 

docs/debugger/how-to-use-the-disassembly-window.md

@@ -1,5 +1,5 @@
 ---
-title: "View Modules, DLLs, and Executables in the Debugger | Microsoft Docs"
+title: "View DLLs and Executables in the Debugger | Microsoft Docs"
 ms.custom: "H1Hack27Feb2017"
 ms.date: "11/04/2016"
 ms.reviewer: ""
@@ -43,15 +43,16 @@ translation.priority.ht:
   - "zh-cn"
   - "zh-tw"
 ---
-# How to: Use the Modules Window in the Visual Studio Debugger
+# View DLLs and Executables using the Modules Window in the Visual Studio Debugger
+ 
+The **Modules** window lists the DLLs and executables (EXE) that are used by your program and shows relevant information for each. 
+
 > [!NOTE]
->  This feature is not available for SQL or script debugging.  
+>  This feature is not available for SQL or script debugging. 
   
- The **Modules** window lists the DLLs and EXE that are used by your program and shows relevant information for each.  
+### To display the Modules window  
 
-### To display the Modules window in break mode or in run mode  
-  
--   On the **Debug** menu, choose **Windows**, and then click **Modules**.  
+-   While you are debugging, select **Debug / Windows** and then click **Modules**.  
 
      By default, the **Modules** window sorts modules by load order. However, you can choose to sort by any column.  
 

docs/debugger/how-to-use-the-modules-window.md

@@ -1,5 +1,5 @@
 ---
-title: "View Register Values in the Debugger in Visual Studio | Microsoft Docs"
+title: "View Register Values in the Visual Studio Debugger | Microsoft Docs"
 ms.custom: ""
 ms.date: "11/04/2016"
 ms.reviewer: ""
@@ -43,7 +43,7 @@ translation.priority.ht:
   - "zh-cn"
   - "zh-tw"
 ---
-# Use the Registers Window in the Visual Studio Debugger
+# View Register Values and use the Registers Window in the Visual Studio Debugger
 The Registers window is available only if address-level debugging is enabled in the **Options** dialog box, **Debugging** node, **General** category.  
 
  The **Registers** window displays register contents. If you keep the **Registers** window open as you step through your program, you can see register values change as your code executes. Values that have changed recently are displayed in red. You can edit register values. For more information, see [How to: Edit a Register Value](../debugger/how-to-edit-a-register-value.md).  

docs/debugger/how-to-use-the-registers-window.md

@@ -1,7 +1,7 @@
 ---
 title: "Debug a multithreaded application using the Threads window | Microsoft Docs"
-ms.custom: ""
-ms.date: "04/18/2017"
+ms.custom: "H1HackMay2017"
+ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 

docs/debugger/how-to-use-the-threads-window.md

@@ -1,7 +1,7 @@
 ---
-title: "Just My Code | Microsoft Docs"
+title: "Debug user code with Just My Code | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -29,19 +29,21 @@ translation.priority.mt:
   - "pt-br"
   - "tr-tr"
 ---
-# Just My Code
-Developers who use .NET Framework languages are familiar with the Just My Code debugger feature that steps over system, framework, and other non-user calls and collapses those calls in the call stack windows. Just My Code has been extended to the C++ and JavaScript languages. This topic describes the specifics of using Just My Code in .NET Framework, native C++, and JavaScript projects.  
+# Specify whether to debug only user code using Just My Code in Visual Studio
+Developers who use .NET Framework languages are familiar with the Just My Code debugger feature that steps over system, framework, and other non-user calls and collapses those calls in the call stack windows. Just My Code has been extended to the C++ and JavaScript languages. This topic describes the specifics of using Just My Code in .NET Framework, native C++, and JavaScript projects.
+
+For most programming languages, Just My Code is enabled by default. 
 
 ##  <a name="BKMK_Enable_or_disable_Just_My_Code"></a> Enable or disable Just My Code  
- To enable or disable Just My Code, choose **Options and Settings** on the **Debug** menu. In the **Debugging** / **General** node, choose or clear **Enable Just My Code**.  
+ To enable or disable Just My Code, choose the **Tools / Options** menu. In the **Debugging** / **General** node, choose or clear **Enable Just My Code**.  
 
  ![Enable Just My Code in the Options dialog box](../debugger/media/dbg_justmycode_options.png "DBG_JustMyCode_Options")  
 
 > [!NOTE]
 >  The **Enable Just My Code** setting is a global setting that is applied to all Visual Studio projects in all languages.  
   
-###  <a name="BKMK_Override_call_stack_filtering"></a> Override call stack filtering  
- In call stack displays, such as the Call Stack and Tasks windows, Just My Code collapses non-user code into an annotated frame labeled `[External Code]`. To view the collapsed frames, choose **Show External Code** on the context menu of the call stack display.  
+###  <a name="BKMK_Override_call_stack_filtering"></a> Show non-user code in call stack views  
+ In views that show the call stack, such as the **Call Stack** and **Tasks** windows, Just My Code collapses non-user code into an annotated frame labeled `[External Code]`. To view the collapsed frames, choose **Show External Code** on the context menu of the call stack display.  
 
 > [!NOTE]
 >  The **Show External Code** setting is saved to the current user's profiler. It is applied to all projects in all languages that are opened by the user.  

docs/debugger/just-my-code.md

@@ -1,7 +1,7 @@
 ---
-title: "Map methods on the call stack while debugging in Visual Studio | Microsoft Docs"
+title: "Create a visual map of the call stack | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -49,16 +49,18 @@ translation.priority.ht:
   - "zh-cn"
   - "zh-tw"
 ---
-# Map methods on the call stack while debugging in Visual Studio
-Create a code map to visually trace the call stack while you're debugging. You can make notes on the map to track what the code is doing so you can focus on finding bugs.  
-  
- ![Debugging with call stacks on code maps](../debugger/media/debuggermap_overview.png "DebuggerMap_Overview")  
-  
+# Create a visual map of the call stack while debugging in Visual Studio Enterprise
+Create a code map to visually trace the call stack while you're debugging. You can make notes on the map to track what the code is doing so you can focus on finding bugs.
+
  You'll need:  
 
 -   [Visual Studio Enterprise](https://www.visualstudio.com/downloads/download-visual-studio-vs)  
 
 -   Code that you can debug, such as Visual C# .NET, Visual Basic .NET, C++, JavaScript, or X++  
+
+Here's a quick look at a code map:
+  
+ ![Debugging with call stacks on code maps](../debugger/media/debuggermap_overview.png "DebuggerMap_Overview")  
 
  See:  
 

docs/debugger/map-methods-on-the-call-stack-while-debugging-in-visual-studio.md

@@ -1,7 +1,7 @@
 ---
 title: "Remote Debugger Port Assignments | Microsoft Docs"
-ms.custom: ""
-ms.date: "03/28/2017"
+ms.custom: "H1Hack27Feb2017"
+ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 

docs/debugger/media/dbg_justmycode_options.png

@@ -7,7 +7,7 @@ ms.suite: ""
 ms.technology: 
   - "vs-ide-debug"
 ms.tgt_pltfrm: ""
-ms.topic: "hero-article"
+ms.topic: "article"
 ms.assetid: 9cb339b5-3caf-4755-aad1-4a5da54b2a23
 caps.latest.revision: 6
 author: "mikejo5000"

docs/debugger/remote-debugger-port-assignments.md

@@ -1,7 +1,7 @@
 ---
 title: "Walkthrough: Debugging a Parallel Application | Microsoft Docs"
-ms.custom: ""
-ms.date: "11/04/2016"
+ms.custom: "H1HackMay2017"
+ms.date: "05/18/2017"
 ms.reviewer: ""
 ms.suite: ""
 ms.technology: 
@@ -41,7 +41,7 @@ translation.priority.ht:
   - "zh-cn"
   - "zh-tw"
 ---
-# Walkthrough: Debugging a Parallel Application
+# Walkthrough: Debugging a Parallel Application in Visual Studio
 This walkthrough shows how to use the **Parallel Tasks** and **Parallel Stacks** windows to debug a parallel application. These windows help you understand and verify the runtime behavior of code that uses the [Task Parallel Library (TPL)](http://msdn.microsoft.com/Library/b8f99f43-9104-45fd-9bff-385a20488a23) or the [Concurrency Runtime](/cpp/parallel/concrt/concurrency-runtime). This walkthrough provides sample code that has built-in breakpoints. After the code breaks, the walkthrough shows how to use the **Parallel Tasks** and **Parallel Stacks** windows to examine it.  
 
  This walkthrough teaches these tasks:  

docs/debugger/remote-debugging-aspnet-on-a-remote-iis-7-5-computer.md

@@ -43,7 +43,7 @@ You can use the VSIX Project template to create an extension or to package an ex
 
     1.  Open the project from which to create a template. This project can be of any project type.  
 
-    2.  On the **File** menu, click **Export Template**. Complete the steps of the wizard.  
+    2.  On the **Project** menu, click **Export Template**. Complete the steps of the wizard.  
 
          A .zip file is created in %USERPROFILE%\My Documents\Visual Studio *\<version>*\My Exported Templates\\.