You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/debugger/autos-and-locals-windows.md
+8-2Lines changed: 8 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Inspect variables - Autos and Locals windows
3
3
description: Inspect variables in the Autos and Locals windows while debugging in Visual Studio. The Autos and Locals windows show variable values while you are debugging.
4
-
ms.date: 07/25/2024
4
+
ms.date: 09/06/2024
5
5
ms.topic: how-to
6
6
f1_keywords:
7
7
- vs.debug.autos
@@ -78,7 +78,7 @@ To make your search more or less thorough, use the **Search Deeper** dropdown li
78
78
> [!NOTE]
79
79
> This feature is supported for .NET Core 3.0 or higher.
80
80
81
-
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.
81
+
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 are 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.
82
82
83
83

84
84
@@ -103,6 +103,12 @@ Set a breakpoint and start debugging. When the breakpoint is hit, execution paus
103
103

104
104
::: moniker-end
105
105
106
+
::: moniker range=">= vs-2022"
107
+
## Get AI assistance
108
+
109
+
If you have [Copilot](../ide/visual-studio-github-copilot-extension.md), you can get AI assistance while you're looking at variables in the Autos or Locals windows, or in data tips. Right-click on a variable and use the **Ask Copilot** button. In this scenario, Copilot already knows the context for your question, so you don't need to provide context yourself in chat. For more information, see [Debug with Copilot](../debugger/debug-with-copilot.md).
110
+
::: moniker-end
111
+
106
112
## <aname="bkmk_whatvariables"></a> Variables in the Autos window (C#, C++, Visual Basic, Python)
107
113
108
114
Different code languages display different variables in the **Autos** window.
Copy file name to clipboardExpand all lines: docs/debugger/debug-with-copilot.md
+6-2Lines changed: 6 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Debug with GitHub Copilot
3
3
description: Use Copilot to help debug your apps and provide performance insights.
4
-
ms.date: 05/21/2024
4
+
ms.date: 09/06/2024
5
5
ms.topic: how-to
6
6
dev_langs:
7
7
- CSharp
@@ -26,6 +26,7 @@ In this article, you'll learn how to debug more efficiently using GitHub Copilot
26
26
In addition, Copilot provides more precise help for a few targeted scenarios including the following:
27
27
28
28
- Exceptions
29
+
- Variables
29
30
- Deadlocks
30
31
- Auto Insights for CPU Usage
31
32
@@ -98,6 +99,9 @@ The following simple example shows how to get AI assistance using the inline Cha
98
99
99
100
1. Right-click in the code and choose **Ask Copilot** to open the inline Chat view.
100
101
102
+
> [!TIP]
103
+
> Alternatively, you can right-click a variable in the Autos or Locals window, or in a data tip, and choose **Ask Copilot**. This provides Copilot with the variable name and context, so you don't need to provide context yourself in the chat.
104
+
101
105
1. Type the following question in the inline Chat view:
102
106
103
107
```
@@ -215,6 +219,6 @@ In this example, we show AI suggestions for a conditional breakpoint. For tracep
215
219
216
220
In addition to interactive debugging assistance, Copilot provides detailed information in the CPU Usage [Auto Insights](../profiling/cpu-insights.md). It provides information and insights related to a set of specific performance insights. With Copilot, ask questions about functions on the identified hot paths in your code, which can help you produce more efficient or cost-effective code.
217
221
218
-
When the CPU Usage tool provides auto insights in the Top Insights section, select**Ask Copilot** to learn from Copilot and start asking questions.
222
+
The **Ask Copilot** button appears even if no specific performance insights are identified. Select**Ask Copilot** to learn from Copilot and start asking questions.
219
223
220
224
[](../debugger/media/vs-2022/debug-with-copilot-top-insights.gif#lightbox)
Copy file name to clipboardExpand all lines: docs/debugger/view-data-values-in-data-tips-in-the-code-editor.md
+11-5Lines changed: 11 additions & 5 deletions
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: View and change variable values with data tips
3
-
description: Use data tips while debugging code in the Visual Studio code editor to view and change variable values like arrays and structures.
4
-
ms.date: 08/14/2024
3
+
description: Use data tips while debugging code in the Visual Studio Code editor to view and change variable values like arrays and structures.
4
+
ms.date: 09/06/2024
5
5
ms.topic: how-to
6
6
dev_langs:
7
7
- CSharp
@@ -17,7 +17,7 @@ ms.author: mikejo
17
17
manager: mijacobs
18
18
ms.subservice: debug-diagnostics
19
19
20
-
#customer intent: As a developer, I want to use data tips in the Visual Studio code editor, so I can view and change variable values when I debug my code.
20
+
#customer intent: As a developer, I want to use data tips in the Visual Studio Code editor, so I can view and change variable values when I debug my code.
21
21
---
22
22
23
23
# View and change variable values with DataTips in the code editor
@@ -67,7 +67,7 @@ When you hover over a variable to view the data tip, you can make the data tip t
67
67
68
68
To enable transparency, follow these steps:
69
69
70
-
1. In the Visual Studio code editor, select inside a data tip, and then select and hold Ctrl.
70
+
1. In the Visual Studio Code editor, select inside a data tip, and then select and hold Ctrl.
71
71
72
72
1. To maintain transparency, continue to hold Ctrl.
73
73
@@ -99,7 +99,7 @@ You can pin a data tip to keep it open on the code editor surface. You can also
99
99
100
100
To pin a data tip, follow these steps:
101
101
102
-
1. In the Visual Studio code editor, hover over a variable to show the data tip.
102
+
1. In the Visual Studio Code editor, hover over a variable to show the data tip.
103
103
104
104
1. In the data tip, use the pushpin to select **Pin to source**:
105
105
@@ -231,6 +231,12 @@ The following image shows the various options on the right-click menu for the me
231
231
232
232
::: moniker-end
233
233
234
+
::: moniker range=">= vs-2022"
235
+
## Get AI assistance
236
+
237
+
If you have [Copilot](../ide/visual-studio-github-copilot-extension.md), you can get AI assistance while you're looking at variables in data tips. Right-click on a variable and use the **Ask Copilot** button. In this scenario, Copilot already knows the context for your question, so you don't need to provide context yourself in chat. For more information, see [Debug with Copilot](../debugger/debug-with-copilot.md).
238
+
::: moniker-end
239
+
234
240
## Visualize complex data types
235
241
236
242
Visualizers display information in a more meaningful, and sometimes graphical, manner. Examples of visualizers include XML, HTML, JSON, and the [Text Visualizer](../debugger/string-visualizer-dialog-box.md). You can use visualizations to examine complex data types in your code during debugging.
Copy file name to clipboardExpand all lines: docs/install/install-visual-studio.md
+10-2Lines changed: 10 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
title: Install Visual Studio and choose your preferred features
3
3
titleSuffix: ''
4
4
description: Learn how to install Visual Studio quickly. To reduce the installation footprint, choose your preferred features.
5
-
ms.date: 06/18/2024
5
+
ms.date: 09/06/2024
6
6
ms.custom: vs-acquisition
7
7
ms.topic: install-set-up-deploy
8
8
helpviewer_keywords:
@@ -270,7 +270,15 @@ You can reduce the installation footprint of Visual Studio on your system drive.
270
270
>
271
271
> If you installed Visual Studio on your computer before, you won't be able to change the **Shared components, tools, and SDKs** path. It appears greyed out. This location is shared by all installations of Visual Studio.
272
272
273
-
## Step 8 - Start developing
273
+
## Step 8 - Sign in to your account (optional)
274
+
275
+
While you don't have to sign in, there are many [advantages](../ide/signing-in-to-visual-studio.md#benefits-why-sign-in) to doing so.
276
+
277
+
You can evaluate a free trial of [Visual Studio Professional or Visual Studio Enterprise](https://visualstudio.microsoft.com/vs/compare/) for 30 days. If you sign in, you can extend the trial period to 90 days. The 90-day trial extension works only one time. To continue using Visual Studio after a trial period ends, unlock it with an [online subscription](../ide/how-to-unlock-visual-studio.md#use-an-online-subscription) or a [product key](../ide/how-to-unlock-visual-studio.md#enter-a-product-key).
278
+
279
+
Visual Studio Community doesn't require you to sign in. However, if the installation prompts you to sign in periodically, [sign in](../ide/signing-in-to-visual-studio.md) to continue using Visual Studio Community without interruptions.
280
+
281
+
## Step 9 - Start developing
274
282
275
283
After installation is complete, you can get started developing with Visual Studio.
0 commit comments