How to: Attach to Script
This topic applies to:
Edition |
Visual Basic |
C# |
C++ |
Web Developer |
|---|---|---|---|---|
Express |
.gif "Topic does not apply") |
|
|
|
Standard |
.gif "Topic applies") |
|
|
|
Pro and Team |
|
|
|
|
Table legend:
|
Applies |
|
Does not apply |
.gif "Topic applies but command hidden by default") |
Command or commands hidden by default. |
This topic explains how to manually attach the Visual Studio debugger to a script file for debugging.
To attach to a running process
On the Debug menu, choose Attach to Process. (If no project is open, choose Attach to Process on the Tools menu.)
In the Attach to Process dialog box, look at the Available Processes list and find the script process you want to attach to. You can identify script processes by looking at the Type column.
If the process you want to debug is running on another computer, you must first select the remote computer. For more information, see How to: Select a Remote Computer.
If the process is running under a different user account, select the Show processes from all users check box.
If you are connected through Remote Desktop Connection, select the Show processes in all sessions check box.
Click the process you want to attach to.
In the Attach to box, you should see Script code or Automatic: Script code. If you see anything else, follow these steps:
Click Select.
In the Select Code Type dialog box, click Debug these code types and select Script.
Click OK.
Click Attach.
At this point, you might see a warning telling you that script debugging is disabled in Internet Explorer. If that occurs, see Warning: Script Debugging Disabled.
The Available Processes list is displayed automatically when you open the Processes dialog box. Processes can start and stop in the background while the dialog box is open. Therefore, the contents might not always be current. You can refresh the list at any time to see the current list of processes by pressing the Refresh button.
You can be attached to multiple programs when you are debugging, but only one program is active in the debugger at any time. You can set the active program in the Debug Location toolbar. For more information, see How to: Set the Current Process.
All Debug menu execution commands affect the active program. You can break any debugged program from the Processes dialog box. For more information, see How to: Break Execution.
Note
If you try to attach to a process that is owned by an untrusted user account, a security warning dialog confirmation will appear. For more information, see Security Warning: Attaching to a process owned by an untrusted user can be dangerous. If the following information looks suspicious or you are unsure, do not attach to this process.
In some cases, when you are debugging in a Terminal Services (Remote Desktop) session, the Available Processes list will not display all available processes. On Windows Server 2003 or later versions, if you are running Visual Studio as a limited user, the Available Processes list will not show processes running in Session 0, which is used for services and other server processes, including w3wp.exe. You can solve the problem by running Visual Studio under an administrator account or by running Visual Studio from the server console rather than a Terminal Services session. If neither of those workarounds is possible, a third option is to attach to the process by typing vsjitdebugger.exe -p ProcessId at the Windows command line. You can determine the process id by using tlist.exe. To obtain tlist.exe, download and install Debugging Tools for Windows, available at Windows Hardware Developer Central.
See Also
Tasks
How to: Attach to Managed Device Processes