Running in Debug Mode

Run your application in debug mode to test its execution.

There are many ways to control execution in the debugger; you can specify that it execute the application and stop either at each line (stepping), or at locations that you set (breakpoints). When execution halts temporarily at a line or breakpoint, use the debugger functions to examine the application at that point. When you are done examining the application context, tell the debugger to continue executing to the next line or breakpoint. You can execute through an entire application in this controlled way.

During your debugger session, your application is either running or it is in break mode. Most debugger functions are available only in break mode.

During debugging, you cannot edit your application: you can examine its status, add and remove breakpoints, and even modify variable values, but you cannot modify the code. You must end the debugger session and return to design mode in .

To start the debugger, use one of these methods:
- To step into your current application, select Debug > Step Into. The application runs to the first executable line of code.
- If you have defined breakpoints and want to stop at the first breakpoint, select Debug > Debug project . If your solution has more than one project, click Debug in the toolbar to select a different project.
The debugger breaks execution at the first executable line or breakpoint, depending on your starting method. The debugger and your application are now in break mode. The variables in the current scope are loaded in any open variable and watch windows, and most debugger functions are now available from the menus.
To continue execution to the next breakpoint, click Continue or select Debug > Continue.
To step through an application without entering functions, click Step Over or select Debug > Step Over.
Each function is executed as a single statement.
To enter functions as you step through the application, click Step Into or select Debug > Step Into.
Execution stops at statements within functions.
If you step into a function but do not want to step into its statements, click Step Out or select Debug > Step Out.
The debugger continues execution until the function returns.
To run to a function on the call stack:
1. If the debugger is not in break mode, click Break All or select Debug > Break All.
2. Open the Call Stack window if it is not open: select Debug > Windows > Call Stack.
3. In the Call Stack window, right-click the function name and choose Run To Cursor.
  The application runs to the first executable line of the specified function, and opens the function in the Script Editor.
To bypass a section of code or return to a statement:
1. In the Script Editor, find the yellow arrow icon in the margin that marks the next statement to be executed.
2. Click and drag the arrow icon to the new location where you want execution to resume.
Setting the next statement can be useful for avoiding a section of code that contains a known bug.
To stop debugging, click Debug > Stop Debugging.
ends the debugging session and returns to design mode.