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/attach-to-running-processes-with-the-visual-studio-debugger.md
+6-1Lines changed: 6 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Attach to running processes with the debugger
3
3
description: Attach the Visual Studio debugger to a running process on a local or remote computer to debug running apps, apps not created in Visual Studio, and other scenarios.
4
-
ms.date: "04/24/2024"
4
+
ms.date: "01/31/2025"
5
5
ms.topic: "conceptual"
6
6
f1_keywords:
7
7
- "vs.debug.processes.attach"
@@ -25,6 +25,7 @@ author: "mikejo5000"
25
25
ms.author: "mikejo"
26
26
manager: mijacobs
27
27
ms.subservice: debug-diagnostics
28
+
zone_pivot_groups: programming-languages-set-one
28
29
---
29
30
30
31
# Attach to running processes with the Visual Studio debugger
@@ -36,6 +37,7 @@ You can use **Attach to Process** to debug running apps on local or remote compu
36
37
> [!TIP]
37
38
> Not sure whether to use **Attach to Process** for your debugging scenario? See [Common debugging scenarios](#BKMK_Scenarios).
38
39
40
+
::: zone pivot="programming-language-dotnet,programming-language-dotnetf,programming-language-cpp,programming-language-all"
39
41
## <aname="BKMK_Attach_to_a_running_process"></a> Attach to a running process on your local machine
40
42
41
43
To quickly reattach to a process you attached to previously, see [Reattach to a process](#BKMK_reattach).
@@ -112,6 +114,7 @@ To attach to a process on your local computer:
112
114
113
115
> [!NOTE]
114
116
> You can be attached to multiple apps for debugging, but only one app is active in the debugger at a time. You can set the active app in the Visual Studio **Debug Location** toolbar or **Processes** window.
117
+
::: zone-end
115
118
116
119
## <aname="BKMK_Attach_to_a_process_on_a_remote_computer"></a> Attach to a process on a remote computer
117
120
@@ -224,6 +227,7 @@ In some cases, when you debug in a Remote Desktop (Terminal Services) session, t
224
227
225
228
If neither of those workarounds is possible, a third option is to attach to the process by running `vsjitdebugger.exe -p <ProcessId>` from the Windows command line. You can determine the process ID using *tlist.exe*. To obtain *tlist.exe*, download and install Debugging Tools for Windows, available at [WDK and WinDbg downloads](/windows-hardware/drivers/download-the-wdk).
226
229
230
+
::: zone pivot="programming-language-dotnet"
227
231
::: moniker range=">= vs-2022"
228
232
229
233
## Attach to a .NET Core process running on Azure App Service (Windows)
@@ -243,6 +247,7 @@ If you're publishing to Azure App Service (Windows), you'll find the **Attach De
243
247
## Attach to a .NET Core process running on Linux using SSH
244
248
245
249
For more information, see [Remote debug .NET Core running on Linux using SSH](../debugger/remote-debugging-dotnet-core-linux-with-ssh.md).
250
+
::: zone-end
246
251
247
252
## <aname="BKMK_Linux_Docker_Attach"></a> Attach to a process running on a Docker container
Copy file name to clipboardExpand all lines: docs/debugger/debug-with-copilot.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,7 +23,7 @@ monikerRange: '>= vs-2022'
23
23
24
24
In this article, you'll learn how to debug more efficiently using GitHub Copilot. Copilot can provide code fixes along with in-depth analysis and explanations of how code works. It helps with proposed fixes to bugs, and explains things such as exceptions. Copilot understands call stacks, frames, variable names, and values. As a result, you can interact with the debugger-aware AI to ask detailed questions related to your code and to debugging issues in general.
25
25
26
-
In addition, Copilot provides more precise help for some targeted scenarios, such as Exceptions, and all those described in [Targeted scenarios for AI assistance](#targeted-scenarios-for-ai-assistance). In most of these scenarios, look for the **Ask Copilot** button. In these scenarios, Copilot already knows the context for your questions.
26
+
In addition, Copilot provides more precise help for some targeted scenarios, such as Exceptions, and all those described in [AI-enhanced scenarios for debugging](#ai-enhanced-scenarios). In most of these scenarios, look for the **Ask Copilot** button. In these scenarios, Copilot already knows the context for your questions.
27
27
28
28
For more information on GitHub Copilot Completions in Visual Studio, see [About GitHub Copilot Completions in Visual Studio](../ide/visual-studio-github-copilot-extension.md).
29
29
@@ -208,13 +208,13 @@ In this example, we show AI suggestions for a conditional breakpoint. For tracep
208
208
209
209
When the debugger pauses at the breakpoint, check the value of `item` and verify that the current value is `Fred`.
210
210
211
-
## Targeted scenarios for AI assistance
211
+
## AI-enhanced scenarios
212
212
213
213
Copilot understands call stacks, frames, variable names, and values. As a result, you can interact with the debugger-aware AI to ask detailed questions related to your code and to debugging issues in general.
214
214
215
215
In addition, Copilot provides more precise help for some targeted scenarios, such as those described in the following table.
216
216
217
-
|Scenario|Link|
217
+
|Feature or scenario|Link|
218
218
|-|-|
219
219
|Exceptions|See [Debug an exception with Copilot](#debug-an-exception-with-copilot) in this article. Help with exceptions includes help with deadlock detection errors.|
220
220
|Variables|See [Debug using Copilot](#debug-using-copilot) in this article.|
Copy file name to clipboardExpand all lines: docs/javascript/write-and-edit-code.md
+17Lines changed: 17 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,6 +91,23 @@ Right-click on `render` and choose **Peek Definition** from the content menu. Or
91
91
92
92
Close the peeked definition window by choosing the small box with an "x" at the top right of the pop-up window.
93
93
94
+
::: moniker range=">=vs-2022"
95
+
## View inlay hints
96
+
97
+
Starting in Visual Studio 2022 version 17.12, inlay hints show additional information about source code that is rendered inline. This is usually used to show inferred types, parameter names, and other implicit information from your code directly in your editor.
98
+
99
+

100
+
101
+
To configure inlay hints:
102
+
103
+
1. Go to **Tools > Options > Text Editor > All Languages > Inlay Hints**, and select an option for viewing inlay hints.
104
+
105
+
1. Go to **Tools > Options > Text Editor > JavaScript/TypeScript > Advanced > General** and configure the inlay hints you want to hide or show.
106
+
107
+
By default, most of these options are disabled.
108
+
109
+
::: moniker-end
110
+
94
111
## Use code snippets
95
112
96
113
Visual Studio provides useful *code snippets* that you can use to quickly and easily generate commonly used code blocks. [Code snippets](../ide/code-snippets.md) are available for different programming languages including JavaScript. Let's add a `for` loop to your code file.
0 commit comments