Export (0) Print
Expand All

Processes Dialog Box

Visual Studio .NET 2003

The Processes dialog box opens when you select Debug Processes from the Tools menu or (with a project open) when you choose Processes from the Debug menu.

The Processes dialog box enables you to view and manipulate programs in a Visual Studio solution. Using this dialog box, you can debug multiple programs at the same time in a single solution.

Transport list box
For remote debugging, enables you to select a DCOM-based remote connection (Default), Native-only Pipe, or Native-only TCP/IP. Select Native-only Pipe if you are debugging a native C/C++ program and you cannot use DCOM for some reason.

Native-only TCP/IP is less secure than Native-only Pipe, but is significantly faster, so you may want to use Native-only TCP/IP if network speed is an issue.

Native-only Pipe is not supported on Windows 95, Windows 98, or Windows Me. If you are debugging an application on one of those platforms, use Native-only TCP/IP rather than Native-only Pipe.

Name list box
Specifies the local machine name or a remote machine name for attaching to a program for debugging. Click the ellipsis () button to browse for a machine on the selected transport.

Available Processes

This group displays information on all programs available for debugging.

Process column
Displays the program or process name (usually an EXE filename).
ID column
Displays the process identification number assigned by the operating system.
Title column
Displays the title in the program's title bar, if any. This title also appears in the taskbar.
Type column
Displays the type of program, such as Win32 or COM+.
Session column
When you use Terminal Services or Remote Desktop to connect to another machine, this column shows the terminal session ID.
Debugger column
If the program is currently being debugged, this column identifies the debugger and the machine the debugger is running on. For example, "Visual Studio debugger on UserMachine".
Attach button
Launches the Attach to Process dialog box, which allows you to debug the program selected in Available Processes. For more information, see Attach To Process Dialog Box.
Refresh button
Refreshes the Available Processes list. Because programs can start and stop in real time while the Processes dialog box is open, the Available Processes list may not be up to date. Choose this button to refresh the list.
Show system processes check box
Displays processes created by the operating system.
Show processes in all sessions check box
Displays processes running in all terminal server sessions.

Debugged Processes

This group displays information on all processes currently attached for debugging.

Process column
Displays the program or process name (usually an EXE filename).
ID column
Displays the process identification number assigned by the operating system.
Title column
Displays the title in the program's title bar, if any. This title also appears in the taskbar.
Transport column
Identifies the type of connection used for debugging. For remote debugging, Default means a DCOM-based remote connection. Native-only TCP/IP and Native-only Pipe are available for native C/C++ programs only.
Machine/Port column
Identifies the machine the process is running on and the port through which the debugger is attached to the process.
Break button
Click to break execution of the program selected in Debugged Processes.
Detach button
Click to stop debugging, and to detach from the program selected in Debugged Processes. This does not terminate the program.
Note   To enable native detach on Windows 2000 or Windows NT 4.0, enter the command net start dbgproxy on the command line.
Terminate button
Click to terminate the program selected in Debugged Processes.
When debugging is stopped list box
For the program selected in Debugged Processes, this setting determines whether the program terminates or merely detaches from the debugger and continues to run when you stop debugging.

See Also

Attaching to a Running Program or Multiple Programs | Attach Errors | Detaching Programs | Visual Studio Debugger Model | Setting Up Remote Debugging

Show:
© 2014 Microsoft