Merge pull request #3085 from v-thepet/debugger3

refresh just-in-time-debugging and edit and continue articles

Author: Ja-Dunn

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

@@ -1,7 +1,7 @@
 ---
-title: "Edit and Continue Error Message Dialog Box | Microsoft Docs"
+title: "Edit and Continue error message dialog box| Microsoft Docs"
 ms.custom: ""
-ms.date: "06/22/2017"
+ms.date: "06/22/2018"
 ms.technology: "vs-ide-debug"
 ms.topic: "reference"
 f1_keywords: 
@@ -21,39 +21,27 @@ manager: douge
 ms.workload: 
   - "multiple"
 ---
-# Edit and Continue Error Message Dialog Box
-This dialog box appears when you are debugging in a language that supports Edit and Continue, but **Edit and Continue** is not available for the type of code changes you have made. The error message inside the box provides a more detailed explanation. Possible reasons for seeing this dialog box include:  
+# Edit and Continue error message 
 
--   You tried to edit SQL Server code.
+The **Edit and Continue** error message box appears when you're debugging in a code language that supports Edit and Continue, but Edit and Continue isn't available for the code changes you've made. The error message provides a more detailed explanation. To respond to the dialog, select **OK** to close the dialog box and cancel the edit attempt.  
 
--   You tried to edit optimized code. (You may need to switch from a release build to a debug build.)
+Possible reasons for this error message include:  
 
--   You tried to edit code while it was running (instead of while paused in the debugger). Try [setting a breakpoint](../debugger/using-breakpoints.md) and editing code while paused.
-
--   You tried to edit managed code when unmanaged debugging was enabled. Edit and Continue does not work with [mixed-mode debugging](../debugger/how-to-debug-in-mixed-mode.md).
-
--   You made a code change that is not supported by Edit and Continue in your programming language. For more info, see topics for unsupported code changes in [C#](../debugger/supported-code-changes-csharp.md), [Visual Basic](../debugger/unsupported-edits-in-visual-basic-edit-and-continue.md), and [C++](../debugger/supported-code-changes-cpp.md).
-  
--   You tried to edit code in a program that you attached to rather than starting from the **Debug** menu.  
-  
--   You tried to edit code while debugging a Dr. Watson dump.  
-  
--   You tried to edit code after an unhandled exception occurred and the option "**Unwind the call stack on unhandled exceptions**" was not selected.  
-  
--   You tried to edit code while debugging an embedded runtime application.
-  
--   You tried to edit managed code using .NET Framework version prior to 4.5.1, and the target is a 64-bit application. If you want to use Edit and Continue, you must set the target to x86. (*projectname* **Properties**, **Compile** tab, **Advanced Compiler** setting.).  
-  
--   You tried to edit code in an assembly that was modified during debugging and has been reloaded.  
-  
--   You tried to edit code in an assembly that has not been loaded.  
-  
--   You started debugging an old version of your application (since the new version has build errors).
-  
-## UIElement List  
- **OK**  
- Exit the dialog box and cancel the immediately preceding edit attempt.  
-  
-## See Also  
- [C++ Edit and Continue blog post](https://blogs.msdn.microsoft.com/vcblog/2016/07/01/c-edit-and-continue-in-visual-studio-2015-update-3/)  
- [Supported Code Changes (C++)](../debugger/supported-code-changes-cpp.md)
+-   Trying to edit SQL Server code.
+-   Trying to edit optimized code. You may need to switch from a release build to a debug build.
+-   Trying to edit code while it's running, instead of while paused in the debugger. Try [setting a breakpoint](../debugger/using-breakpoints.md), and editing the code while paused.
+-   Trying to edit managed code when only unmanaged debugging is enabled. Edit and Continue doesn't work with [mixed-mode debugging](../debugger/how-to-debug-in-mixed-mode.md).
+-   Making a code change that isn't supported by Edit and Continue in your programming language. For more information, see articles about [supported code changes in C#](supported-code-changes-csharp.md), [unsupported edits in Visual Basic Edit and Continue](unsupported-edits-in-visual-basic-edit-and-continue.md), and [supported C++ code changes](supported-code-changes-cpp.md).
+-   Trying to edit code in an app you're attached to, instead of starting debugging from the **Debug** menu.  
+-   Trying to edit code while debugging a Dr. Watson dump.  
+-   Trying to edit code after an unhandled exception occurs, and the option **Unwind the call stack on unhandled exceptions** is not selected.  
+-   Trying to edit code while debugging an embedded runtime application.
+-   Trying to edit managed code using a .NET Framework version earlier than 4.5.1 with a 64-bit app target. To use Edit and Continue for .NET Framework earlier than 4.5.1, set the target to **x86** in the **\<ProjectName>** > **Properties** > **Compile** tab, **Advanced Compiler** setting.  
+-   Trying to edit code in an assembly that was modified during debugging and has been reloaded.  
+-   Trying to edit code in an assembly that hasn't been loaded.  
+-   Starting to debug an old version of an app, because the latest version has build errors.
+  
+For more information, see:
+- [C++ Edit and Continue blog post](https://blogs.msdn.microsoft.com/vcblog/2016/07/01/c-edit-and-continue-in-visual-studio-2015-update-3/)  
+- [Supported code changes (C++)](../debugger/supported-code-changes-cpp.md)
+- [Edit and Continue](../debugger/edit-and-continue.md)

docs/debugger/edit-and-continue-error-message-dialog-box.md

@@ -1,7 +1,7 @@
 ---
-title: "How to: Enable and Disable Edit and Continue (C#, VB, C++) | Microsoft Docs"
+title: "How to: Enable and disable Edit and Continue (C#, VB, C++) | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/04/2018"
 ms.technology: "vs-ide-debug"
 ms.topic: "conceptual"
 dev_langs: 
@@ -28,35 +28,28 @@ ms.workload:
   - "dotnet"
   - "cplusplus"
 ---
-# How to: Enable and Disable Edit and Continue (C#, VB, C++)
-You can disable or enable Edit and Continue in the **Options** dialog box at design time. You cannot change this setting while you are debugging.  
+# How to: Enable and disable Edit and Continue (C#, VB, C++)
+
+You can disable or enable **Edit and Continue** in the Visual Studio **Options** dialog box at design time. **Edit and Continue** works only in debug builds. For more information, see [Edit and Continue](../debugger/edit-and-continue.md). 
 
-Edit and Continue works only in debug builds. For native C++, Edit and Continue requires using the /INCREMENTAL option. For more information about feature requirements in C++, see this [blog post](https://blogs.msdn.microsoft.com/vcblog/2016/07/01/c-edit-and-continue-in-visual-studio-2015-update-3/) and [Edit and Continue (Visual C++)](../debugger/edit-and-continue-visual-cpp.md).
+For native C++, **Edit and Continue** requires using the `/INCREMENTAL` option. For more information about feature requirements in C++, see this [blog post](https://blogs.msdn.microsoft.com/vcblog/2016/07/01/c-edit-and-continue-in-visual-studio-2015-update-3/) and [Edit and Continue (Visual C++)](../debugger/edit-and-continue-visual-cpp.md).
 
-#### To enable/disable Edit and Continue  
+**To enable or disable Edit and Continue:**  
 
-1.  If you are in a debugging session, stop debugging (**Shift + F5**).
+1.  If you're in a debugging session, stop debugging (**Debug** > **Stop Debugging** or **Shift**+**F5**).
 
-2.  Open debugging options page (**Tools > Options > Debugging**).
-  
-3.  Select **General**, and scroll down to **Edit and Continue** category (right pane).  
-  
-4.  To enable, select the **Enable Edit and Continue** check box. To disable, clear the check box.  
+1.  In **Tools** > **Options** > (or **Debug** > **Options**) > **Debugging** > **General**, select **Edit and Continue** in the right pane.  
 
     > [!NOTE]
     >  If IntelliTrace is enabled and you collect both IntelliTrace events and call information, Edit and Continue is disabled. For more information, see [IntelliTrace](../debugger/intellitrace.md).
-
-5. (C++) To enable, select **Enable Native Edit and Continue**. To disable, clear the check box.
-
-6. (C++) Set additional options for native code.
-
+    
+1.  For C++ code, make sure **Enable Native Edit and Continue** is selected, and set the additional options:
     - **Apply changes on continue (Native only)**  
-        Visual Studio automatically compiles and applies any outstanding code changes you have made when continuing the process from a break state. If not selected, you can choose to apply changes using the "Apply Code Changes" item under the Debug menu.  
-  
+      
+      If selected, Visual Studio automatically compiles and applies code changes when you continue debugging from a break state. Otherwise, you can choose to apply changes using **Debug** > **Apply Code Changes**.  
+      
     - **Warn about stale code (Native only)**  
-        Get warnings about stale code. 
-  
-7.  Click **OK**.    
+      
+      If selected, gives warnings about stale code. 
 
-## See Also  
- [Edit and Continue](../debugger/edit-and-continue.md)
+1.  Click **OK**.    

docs/debugger/how-to-enable-and-disable-edit-and-continue.md

@@ -1,7 +1,7 @@
 ---
 title: "How to: Use Edit and Continue (C#) | Microsoft Docs"
 ms.custom: ""
-ms.date: "11/04/2016"
+ms.date: "10/04/2018"
 ms.technology: "vs-ide-debug"
 ms.topic: "conceptual"
 dev_langs: 
@@ -19,31 +19,29 @@ ms.workload:
   - "dotnet"
 ---
 # How to: Use Edit and Continue (C#)
-With Edit and Continue for C#, you can make changes to your code in break mode while debugging. The changes can be applied without having to stop and restart the debugging session.  
-  
- Edit and Continue is invoked automatically when you make changes in break mode, then choose a debugger execution command, such as **Continue**, **Step**, or **Set Next Statement**, or evaluate a function in a debugger window.  
-  
-> [!NOTE]
->  Edit and Continue is not supported when debugging optimized code, mixed native/managed code, or SQL Server common language runtime (CLR) integration code. For information on other unsupported scenarios, see [Supported Code Changes (C# and Visual Basic)](../debugger/supported-code-changes-csharp.md). If you try to apply code changes in one of these scenarios, the debugger displays a dialog box explaining that Edit and Continue is not supported.  
-  
-### To invoke Edit and Continue automatically  
-  
-1.  In break mode, make a change to your source code.  
-  
-2.  From the **Debug** menu, click **Continue**, **Step**, or **Set Next Statement** or evaluate a function in a debugger window.  
-  
-     The new code is compiled and the debugging continues with the new code. Some changes are not supported by Edit and Continue. For more information, see [Supported Code Changes (C# and Visual Basic)](../debugger/supported-code-changes-csharp.md).  
-  
-### To enable/disable Edit and Continue  
-  
-1.  On the **Tools** menu, click **Options**.  
-  
-2.  In the **Options** dialog box, expand the **Debugging** node, and select **Edit and Continue**.  
-  
-3.  In the **Options** dialog box **Edit and Continue** page, select or clear the **Enable Edit and Continue** check box.  
-  
-     The setting takes effect when you restart the debugging session.  
-  
-## See Also  
- [Edit and Continue (Visual C#)](../debugger/edit-and-continue-visual-csharp.md)   
- [Supported Code Changes (C# and Visual Basic)](../debugger/supported-code-changes-csharp.md)   
+With Edit and Continue, you can make and apply changes to your code in break mode while debugging, without having to stop and restart the debugging session.  
+
+Edit and Continue for C# happens automatically when you make code changes in break mode, then continue debugging by using **Continue**, **Step**, or **Set Next Statement**, or evaluate a function in a debugger window.  
+
+For more information, see [Edit and Continue (Visual C#)](../debugger/edit-and-continue-visual-csharp.md).
+
+>[!NOTE]
+>Edit and Continue is not supported for optimized, mixed, or SQL Server common language runtime (CLR) integration code. For information on other unsupported scenarios, see [Supported code changes (C# and Visual Basic)](../debugger/supported-code-changes-csharp.md). If you try to Edit and Continue with one of these scenarios, a message box appears stating that Edit and Continue is not supported.  
+  
+**To enable or disable Edit and Continue:**  
+   
+1. If you're in a debugging session, stop debugging (**Debug** > **Stop Debugging** or **Shift**+**F5**).
+   
+1. In **Tools** > **Options** (or **Debug** > **Options**) > **Debugging** > **General**, select or clear the **Enable Edit and Continue** check box.  
+  
+The setting takes effect when you start or restart the debugging session.  
+
+**To use Edit and Continue:**  
+   
+1. While debugging, in break mode, make a change to your source code.  
+   
+1. From the **Debug** menu, click **Continue**, **Step**, or **Set Next Statement**, or evaluate a function in a debugger window.  
+   
+   Debugging continues with the new, compiled code. 
+
+Some types of code changes are not supported by Edit and Continue. For more information, see [Supported code changes (C# and Visual Basic)](../debugger/supported-code-changes-csharp.md).   

docs/debugger/how-to-use-edit-and-continue-csharp.md

@@ -1,7 +1,7 @@
 ---
-title: "How to: Respond to the Just-In-Time Debugger | Microsoft Docs"
+title: "Disable the Just-In-Time Debugger | Microsoft Docs"
 ms.custom: ""
-ms.date: "05/23/17"
+ms.date: "05/23/18"
 ms.technology: "vs-ide-debug"
 ms.topic: "troubleshooting"
 helpviewer_keywords:
@@ -14,34 +14,30 @@ manager: douge
 ms.workload:
   - "multiple"
 ---
-# How to: Respond to the Just-In-Time Debugger
+# Disable the Just-In-Time Debugger 
 
-The actions you should take when you see the Just-in-Time debugger dialog box depend on what you are trying to do:
+The Just-In-Time Debugger dialog box may open when an error occurs in a running app, and prevent the app from continuing. 
 
-#### If you want to fix or debug the error (Visual Studio users)
+The Just-In-Time Debugger gives you the option to launch Visual Studio to debug the error. You must have [Visual Studio](http://visualstudio.microsoft.com) or another selected debugger installed to view detailed information about the error or try to debug it. 
 
-- You must have [Visual Studio installed](http://visualstudio.microsoft.com) to view the detailed information about the error and to try to debug it. For more information, see [Debug using the Just-In-Time Debugger](../debugger/debug-using-the-just-in-time-debugger.md). If you cannot resolve the error and fix the app, contact the owner of the app to resolve the error.
+If you're a Visual Studio user and want to try to debug the error, see [Debug using the Just-In-Time Debugger](../debugger/debug-using-the-just-in-time-debugger.md). If you can't fix the error, or want to keep the Just-In-Time Debugger from opening, you can [disable Just-In-Time debugging from Visual Studio](debug-using-the-just-in-time-debugger.md#BKMK_Enabling). 
 
-#### If you want to prevent the Just-In-Time Debugger dialog box from appearing
+If you had Visual Studio installed but no longer do, you may need to [disable Just-In-Time debugging from the Windows registry](debug-using-the-just-in-time-debugger.md#disable-just-in-time-debugging-from-the-windows-registry). 
 
-You can take steps to prevent the Just-in-Time Debugger dialog box from appearing. If the app handles the error, you can run the app normally.
+If you don't have Visual Studio installed, you can prevent Just-In-Time debugging by disabling script debugging or server-side debugging. 
 
-1. (Web apps) If you are trying to run a web app, you can disable script debugging.
+- If you're trying to run a web app, disable script debugging:
+  
+  In Windows **Control Panel** > **Network and Internet** > **Internet Options**, select **Disable script debugging (Internet Explorer)** and **Disable script debugging (other)**. The exact steps and settings depend on your version of Windows and your browser.
+  
+  ![JIT Internet Options](../debugger/media/jitinternetoptions.png "JIT internet options")
+  
+- If you're hosting an ASP.NET web app in IIS, disable server-side debugging:
 
-    For Internet Explorer or Edge, disable script debugging in the Internet Options dialog box. You can access these settings from the **Control Panel** > **Network and Internet** > **Internet Options** (the exact steps depend on your version of Windows and your browser).
+  1. In IIS Manager **Features View**, under the **ASP.NET** section, double-click **.NET Compilation**, or select it and then select **Open Feature** in the **Actions** pane. 
+  1. Under **Behavior** > **Debug**, select **False**. The steps are different in older versions of IIS.
 
-    ![JITInternetOptions](../debugger/media/jitinternetoptions.png "JITInternetOptions")
+After you disable Just-In-Time debugging, the app may be able to handle the error and run normally. 
 
-    Then reopen the web page where you found the error. If changing this setting does not resolve the issue, contact the owner of the web app to fix the issue.
+If the app still has an unhandled error, you may see an error message, or the app may crash or hang. The app won't run normally until the error is fixed. You can try to contact the owner of the app and ask them to fix it.
 
-3. (Visual Studio users) If you have Visual Studio installed (or if you had it installed previously and removed it), [disable Just-in-Time debugging](../debugger/debug-using-the-just-in-time-debugger.md) and try to run the app again.
-
-    > [!IMPORTANT]
-    > If you disable Just-in-Time debugging and the app encounters an unhandled exception (an error), you will either see a standard error dialog box instead, or the app will crash or hang. The app will not run normally until the error is fixed (by you or the owner of the app).
-
-2. (ASP.NET and IIS) If you are hosting an ASP.NET Web app in IIS, disable server-side debugging.
-
-    In IIS Manager, right-click the server node and choose **Switch to Features View**. Under the ASP.NET section, choose **.NET Compilation** and then make sure you choose **False** as the Debug behavior (the steps are different in older versions of IIS).
-
-## See Also
- [Debugger Basics](../debugger/getting-started-with-the-debugger.md)

docs/debugger/just-in-time-debugging-in-visual-studio.md

@@ -128,7 +128,7 @@
     - name: Debug using the Just-In-Time Debugger
       href: debug-using-the-just-in-time-debugger.md
       items:
-      - name: Respond to the Just-In-Time Debugger
+      - name: Disable the Just-In-Time Debugger
         href: just-in-time-debugging-in-visual-studio.md
   - name: Configure debugging
     items: