Datasheet

❑ Continue — This command resumes program execution. The program runs until it ﬁnishes, it

reaches another breakpoint, or you stop it.

❑ Break All — This command stops execution of all programs running within the debugger. This

may include more than one program if you are debugging more than one application at the same

time. This can be useful, for example, if two programs work closely together.

❑ Stop Debugging — This command halts the program’s execution and ends its debugging ses-

sion. The program stops immediately, so it does not get a chance to execute any cleanup code.

❑ Step Into — This command makes the debugger execute the current line of code. If that code

invokes a function, subroutine, or some other procedure, the point of execution moves into that

procedure. It is not always obvious whether a line of code invokes a procedure. For example, a

line of code that sets an object’s property may be simply setting a value or invoking a property

procedure.

❑ Step Over — This command makes the debugger execute the current line of code. If that code

invokes a function, subroutine, or some other procedure, the debugger calls that routine but

does not step into it, so you don’t need to step through its code. However, if a breakpoint is set

inside that routine, execution will stop at the breakpoint.

❑ Step Out — This command makes the debugger run until it leaves the routine it is currently

executing. Execution pauses when the program reaches the line of code that called this routine.

❑ QuickWatch — This command displays a dialog box that gives information about the selected

code object. Figure 1-21 shows the dialog box displaying information about a

TextBox control

named

txtDirectory. If you look closely, you can see some of the control’s properties includ-

ing

TabIndex, TabStop, Tag, and Text.

Figure 1-21: The QuickWatch dialog box lets you examine an

object’s properties and optionally set a new watch on it.

Chapter 1: IDE

37055c016.qxd 4/8/07 12:46 PM Page 25