Merge pull request #127 from Microsoft/mikejo

Mikejo

Author: Greg Van Liew

docs/debugger/managing-exceptions-with-the-debugger.md

@@ -191,6 +191,17 @@ public class GenericException<T> : Exception
  You can add the exception to **Exception Settings** like this:  
 
  ![adding generic exception](../debugger/media/addgenericexception.png "AddGenericException")  
+
+### Adding Conditions to an Exception
+
+You can set conditions on exceptions in the **Exception Settings** dialog box. Currently supported conditions include the module name(s) to include or exclude for the exception. By setting module names as conditions, you can choose to break for the exception only on particular code modules, or you can avoid breaking on particular modules.
+
+> [!NOTE]
+> Adding conditions to an exception is new in [!include[vs_dev15](../misc/includes/vs_dev15_md.md)]
+
+To add conditional exceptions, choose the **Edit condition** icon in the Exception Settings dialog box or right-click the exception and choose **Edit Conditions**.
+
+![Conditions on an Exception](../debugger/media/dbg-conditional-exception.png "DbgConditionalException")
 
 ## See Also  
  [Continuing Execution After an Exception](../debugger/continuing-execution-after-an-exception.md)   

docs/debugger/media/addgenericexception.png

@@ -113,11 +113,20 @@ Get familiar with commands and shortcuts to navigate code in the debugger and th
 
 -   **Run to the cursor location**  
 
-     To run to the cursor location, place the cursor on an executable line of code in a source window. On the editor's context menu (right-click in the editor), choose **Run to Cursor**. This is like setting a temporary breakpoint.  
+     To run to the cursor location, place the cursor on an executable line of code in a source window. On the editor's context menu (right-click in the editor), choose **Run to Cursor**. This is like setting a temporary breakpoint.
+
+-   **Run to Click** 
+
+    To run to a point in your code while paused in the debugger, select the **Run execution to here** green arrow icon (you see the icon while hovering over a line of code). This eliminates the need to set temporary breakpoints.
+
+    ![Debugger's Run to Click](../debugger/media/dbg-run-to-click.png "DbgRunToClick") 
+
+    > [!NOTE]
+    > **Run to Click** is new in [!include[vs_dev15](../misc/includes/vs_dev15_md.md).
 
 -   **Manually break into code**  
 
-     To break into the next available line of code in an executing app, choose **Debug**, **Break All** (keyboard: **Ctrl+Alt+Break**).  
+     To break into the next available line of code in an executing app, choose **Debug**, **Break All** (keyboard: **Ctrl+Alt+Break**). 
 
      If you break while executing code without corresponding source or symbol (.pdb) files), the debugger displays a **Source Files Not Found** or a **Symbols Not Found** page that can help you find the appropriate files. See [Specify Symbol (.pdb) and Source Files](../debugger/specify-symbol-dot-pdb-and-source-files-in-the-visual-studio-debugger.md). If you can't access the supporting files, you can still debug the assembly instructions in the Disassembly window.  
 

docs/debugger/media/dbg-exception-helper.png

@@ -45,7 +45,7 @@ The debugger includes these new features:
 
 - The **Exception Helper** replaces the Exception Assistant and appears in a non-modal dialog box where the error occurred. The **Exception Helper** provides quicker access to any inner exceptions, additional analysis by the debugger (if available), and immediate access to the **Exception Settings** for the exception. The Exception Helper can also be dragged to a floating view if it is blocking something that you need to see.
 
-    For example, a **NullReferenceException** now shows the variable that has the null reference.
+    For example, a **NullReferenceException** now shows the variable that has the null reference (extra information).
 
     ![Debugger's Exception Helper](../debugger/media/dbg-exception-helper.png "DbgExceptionHelper")