Merge pull request #3055 from MicrosoftDocs/master636906012195577639

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: gewarren

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

@@ -91,7 +91,7 @@ For more information on remote deployment of UWP apps, see [Deploy and debug UWP
 ## See also
 
 - [Debugging in Visual Studio](../debugger/index.md)
-- [Debugger feature tour](../debugger/debugger-feature-tour.md)
+- [First look at the debugger](../debugger/debugger-feature-tour.md)
 - [Remote debugging](../debugger/remote-debugging.md)
 - [Configure the Windows Firewall for remote debugging](../debugger/configure-the-windows-firewall-for-remote-debugging.md)
 - [Remote debugger port assignments](../debugger/remote-debugger-port-assignments.md)

docs/debugger/debugging-managed-code.md

@@ -73,9 +73,6 @@ Discusses debugging .NET Framework applications and the configuration requiremen
 [Debugging Script and Web Applications](/visualstudio/debugger/how-to-enable-debugging-for-aspnet-applications)\
 Describes common debugging problems and techniques you may encounter when debugging script and Web applications.
 
-[Debugging Home Page](../debugger/debugger-feature-tour.md)\
-Provides links to the larger sections of the debugging documentation. Information includes what's new in the debugger, settings and preparation, breakpoints, handling exceptions, edit and continue, debugging managed code, debugging Visual C++ projects, debugging COM and ActiveX, debugging DLLs, debugging SQL, and the user interface references.
-
 ## See also
 
 - [Walkthrough: Debug Custom Windows Forms Controls at Design Time](/dotnet/framework/winforms/controls/walkthrough-debugging-custom-windows-forms-controls-at-design-time)

docs/debugger/general-debugging-options-dialog-box.md

@@ -190,7 +190,7 @@ Enables the Edit and Continue functionality while debugging.
     Get warnings about stale code.
 
 **Show Run to Click button in editor while debugging**:
-When this option is selected, the [Run to Click](debugger-feature-tour.md#run-to-a-point-in-your-code-quickly-using-the-mouse) button will be shown while debugging.
+When this option is selected, the [Run to Click](../debugger/debugger-feature-tour.md#run-to-a-point-in-your-code-quickly-using-the-mouse) button will be shown while debugging.
 
 **Automatically close the console when debugging stops**:
 Tells Visual Studio to close the console at the end of a debugging session.
@@ -219,4 +219,4 @@ When this option is selected, the debugger uses the Visual Studio 2010 native de
 ## See also
 
 - [Debugging in Visual Studio](../debugger/index.md)
-- [Debugger feature tour](../debugger/debugger-feature-tour.md)
+- [First look at the debugger](../debugger/debugger-feature-tour.md)

docs/debugger/media/managed-data-breakpoint.png

@@ -132,4 +132,4 @@ For more information on using edit-and-continue and on feature limitations, see
 In this tutorial, you've learned how to start the debugger, step through code, and inspect variables. You may want to get a high-level look at debugger features along with links to more information.
 
 > [!div class="nextstepaction"]
-> [Debugger feature tour](../debugger/debugger-feature-tour.md)
+> [First look at the debugger](../debugger/debugger-feature-tour.md)

docs/debugger/media/vs-2019/cpu-use-wt-getmaxnumbercalltree-annotated.png

@@ -132,4 +132,4 @@ For more information on using edit-and-continue and on feature limitations, see
 In this tutorial, you've learned how to start the debugger, step through code, and inspect variables. You may want to get a high-level look at debugger features along with links to more information.
 
 > [!div class="nextstepaction"]
-> [Debugger feature tour](../debugger/debugger-feature-tour.md)
+> [First look at the debugger](../debugger/debugger-feature-tour.md)

docs/debugger/media/vs-2019/cpu-use-wt-showexternalcodetoowide-found.png

@@ -180,4 +180,4 @@ For more information on using edit-and-continue and on feature limitations, see
 In this tutorial, you've learned how to start the debugger, step through code, and inspect variables. You may want to get a high-level look at debugger features along with links to more information.
 
 > [!div class="nextstepaction"]
-> [Debugger feature tour](../debugger/debugger-feature-tour.md)
+> [First look at the debugger](../debugger/debugger-feature-tour.md)

docs/debugger/quickstart-debug-aspnet.md

@@ -141,6 +141,28 @@ To visually trace breakpoints during code execution, see [Map methods on the cal
     ```C++
     ((my_class *) 0xcccccccc)->my_method
     ```
+::: moniker range=">= vs-2019"
+
+## <a name="BKMK_set_a_data_breakpoint_managed"></a>Set data breakpoints (.NET Core 3.0 or higher)
+
+Data breakpoints break execution when a specific object's property changes.
+
+**To set a data breakpoint**
+
+1. In a .NET Core project, start debugging, and wait until a breakpoint is reached.
+
+2. In the the **Autos**, **Watch**, or **Locals** window, right-click a property and select **Break when value changes** in the context menu.
+
+    ![Managed Data Breakpoint](../debugger/media/managed-data-breakpoint.png "Managed Data Breakpoint")
+
+Data breakpoints in .NET Core won't work for:
+
+- Properties that are not expandable in the tooltip, Locals, Autos, or Watch window
+- Static variables
+- Classes with the DebuggerTypeProxy Attribute
+- Fields inside of structs 
+
+::: moniker-end
 
 ## <a name="BKMK_set_a_data_breakpoint_native_cplusplus"></a>Set data breakpoints (native C++ only)
 
@@ -150,7 +172,7 @@ To visually trace breakpoints during code execution, see [Map methods on the cal
 
 1.  In a C++ project, start debugging, and wait until a breakpoint is reached. On the **Debug** menu, choose **New Breakpoint** > **Data Breakpoint**
 
-    You can also select **New** > **Data Breakpoint** in the **Breakpoints** window.
+    You can also select **New** > **Data Breakpoint** in the **Breakpoints** window or right-click an item in the **Autos**, **Watch**, or **Locals** window and select **Break when value changes**in the context menu.
 
 2.  In the **Address** box, type a memory address, or an expression that evaluates to a memory address. For example, type `&avar` to break when the contents of the variable `avar` changes.
 

docs/debugger/quickstart-debug-with-cplusplus.md

@@ -81,7 +81,7 @@ In this tutorial, you will:
 
     ![Overview of IntelliTrace step-back](../debugger/media/intellitrace-step-back-overview.png "Overview of IntelliTrace Step-back")
 
-    To learn more about how to inspect variables in Visual Studio, see [Debugger feature tour](../debugger/debugger-feature-tour.md)
+    To learn more about how to inspect variables in Visual Studio, see [First look at the debugger](../debugger/debugger-feature-tour.md)
 
 ## Frequently Asked Questions