Merge pull request #4449 from MicrosoftDocs/master637112758086514763

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

Author: ghogen

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

@@ -65,6 +65,20 @@ Use the left and right arrows (Shift+F3 and F3, respectively) to navigate betwee
 
 To make your search more or less thorough, use the **Search Deeper** dropdown at the top of the **Autos** or **Locals** window to select how many levels deep you want to search into nested objects. 
 
+## Pin properties in the Autos or Locals window
+
+> [!NOTE]
+> This feature is supported for .NET Core 3.0 or higher.
+
+You can quickly inspect objects by their properties in the Autos and Locals windows with the **Pinnable Properties** tool.  To use this tool, hover over a property and select the pin icon that appears or right-click and select the **Pin Member as Favorite** option in the resulting context menu.  This bubbles up that property to the top of the object’s property list, and the property name and value is displayed in the **Value** column.  To unpin a property, select the pin icon again or select the **Unpin Member as Favorite** option in the context menu.
+
+![Pin properties in the Locals window](../debugger/media/basic-pin.gif "Pin properties in the Locals window")
+
+You can also toggle property names and filter out non-pinned properties when viewing the object’s property list in the Autos or Locals windows.  You can access each option by selecting the buttons in the toolbar above the Autos or Locals windows.
+
+![Filter favorite properties](../debugger/media/filter-pinned-properties-locals.png "Filter favorite properties")
+![Toggle property names](../debugger/media/toggle-property-names.gif "Toggle property names")
+
 ::: moniker-end
 
 ## Change the context for the Autos or Locals window

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

@@ -16,9 +16,9 @@ ms.workload:
 
 The Just-In-Time Debugger dialog box may open when an error occurs in a running app, and prevent the app from continuing.
 
-The Just-In-Time Debugger gives you the option to launch Visual Studio to debug the error. You must have [Visual Studio](https://visualstudio.microsoft.com/) or another selected debugger installed to view detailed information about the error or try to debug it.
+The Just-In-Time Debugger gives you the option to launch Visual Studio to debug the error. You must have Visual Studio or another selected debugger installed to view detailed information about the error or try to debug it.
 
-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 your already 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 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).
 

docs/debugger/media/basic-pin-datatip.gif

@@ -88,6 +88,21 @@ You can also pin expanded items to the pinned DataTip by hovering over them and
 
 To edit the value of a variable or element in a DataTip, select the value, type a new value, and press **Enter**. Selection is disabled for read-only values.
 
+::: moniker range=">= vs-2019"
+
+## Pin Properties in DataTips (Supported in Visual Studio 2019 version 16.4 Preview 3 or higher)
+
+> [!NOTE]
+> This feature is supported for .NET Core 3.0 or higher.
+
+You can quickly inspect objects by their properties in DataTips with the **Pinnable Properties** tool.  To use this tool, hover over a property and select the pin icon that appears or right-click and select the **Pin Member as Favorite** option in the resulting context menu.  This bubbles up that property to the top of the object’s property list, and the property name and value is displayed in the right column of the DataTip.  To unpin a property, select the pin icon again or select the **Unpin Member as Favorite** option in the context menu.
+
+![Pinning a property in a DataTip](../debugger/media/basic-pin-datatip.gif "Pinning a property in a DataTip")
+
+You can also toggle property names and filter out non-pinned properties when viewing the object’s property list in a datatip.  You can access either option by right-clicking a row containing a property and selecting the **Show only pinned members** or **Hide pinned member names in values** options in the context menu.
+
+::: moniker-end
+
 ## Visualize complex data types
 
 A magnifying glass icon next to a variable or element in a DataTip means that one or more [visualizers](../debugger/create-custom-visualizers-of-data.md), such as the [Text Visualizer](../debugger/string-visualizer-dialog-box.md), are available for the variable. Visualizers display information in a more meaningful, sometimes graphical, manner.

docs/debugger/media/basic-pin-watch.gif

@@ -97,6 +97,17 @@ Use the left and right arrows (Shift+F3 and F3, respectively) to navigate betwee
 
 To make your search more or less thorough, use the **Search Deeper** dropdown at the top of the **Watch** window to select how many levels deep you want to search into nested objects. 
 
+## Pin properties in the Watch window
+
+>[!NOTE]
+> This feature is supported in .NET Core 3.0 or higher.
+
+You can quickly inspect objects by their properties in the Watch window with the **Pinnable Properties** tool.  To use this tool, hover over a property and select the pin icon that appears or right-click and select the **Pin Member as Favorite** option in the resulting context menu.  This bubbles up that property to the top of the object’s property list, and the property name and value is displayed in the **Value** column.  To unpin a property, select the pin icon again or select the **Unpin Member as Favorite** option in the context menu.
+
+![Pin properties in the Watch window](../debugger/media/basic-pin-watch.gif "Pin properties in the Watch window")
+
+You can also toggle property names and filter out non-pinned properties when viewing the object’s property list in the Watch window.  You can access both options by selecting the buttons in the toolbar above the watch window.
+
 ::: moniker-end
 
 ### <a name="bkmk_refreshWatch"></a> Refresh watch values

docs/debugger/media/basic-pin.gif

@@ -130,7 +130,7 @@ Here are the various types of term that are supported:
 |UserSettingsStoreQuery:\<query>|"query" represents a full path into the user settings store, which must evaluate to a non-zero value. The query is split into a "collection" and "propertyName" at the last slash.|
 |ConfigSettingsStoreQuery:\<query>|"query" represents a full path into the config settings store, which must evaluate to a non-zero value. The query is split into a "collection" and "propertyName" at the last slash.|
 |ActiveProjectFlavor:\<projectTypeGuid>|The term will be true whenever the currently selected project is flavored (aggregated) and has a flavor matching the given project type GUID.|
-|ActiveEditorContentType:\<contentType>|The term will be true when the selected document is a text editor with the given content type.|
+|ActiveEditorContentType:\<contentType>|The term will be true when the selected document is a text editor with the given content type. Note: when the selected document is renamed, this term does not refresh until the file is closed and reopened.|
 |ActiveProjectCapability:\<Expression>|The term is true when active project capabilities match the provided expression. An expression can be something like VB &#124; CSharp.|
 |SolutionHasProjectCapability:\<Expression>|Similar to above but term is true when solution has any loaded project that matches to the expression.|
 |SolutionHasProjectFlavor:\<projectTypeGuid>|The term will be true whenever a solution has project that is flavored (aggregated) and has a flavor matching the given project type GUID.|

docs/debugger/media/filter-favorites.gif

@@ -139,9 +139,9 @@ If an unresponsiveness manifests itself in an unpredictable fashion, on the next
 launch a new instance of Visual Studio and report a problem from that instance.
 In the [“Record”
 screen](https://docs.microsoft.com/visualstudio/ide/how-to-report-a-problem-with-visual-studio?view=vs-2019#record-a-repro),
-be sure to select the Visual Studio session that is hung.
+be sure to select the Visual Studio session that is unresponsive.
 
-If the Visual Studio instance that is hung was launched in Administrator mode,
+If the Visual Studio instance that is unresponsive was launched in Administrator mode,
 then the second instance would also need to be launched in Administrator mode.
 
 >[!NOTE] 

docs/debugger/media/filter-pinned-properties-locals.png

@@ -2,7 +2,7 @@
 title: "Using Visual Studio on an Azure Virtual Machine"
 titleSuffix: ""
 description: "Learn how to use Visual Studio on an Azure Virtual Machine"
-ms.date: 12/04/2019
+ms.date: 12/06/2019
 ms.custom: "seodec18"
 ms.topic: conceptual
 helpviewer_keywords: