About the Code to Profile Pane

The Code to Profile pane is on the right side of the Setup panel and at the top. Using this pane, you can create, modify, remove and configure profiling areas — collections of code elements like classes, routines, units or modules — that specify which code AQTime will include in or exclude from profiling tasks.

For complete information on areas, their types and profiling levels, see About Areas.

Some profilers do not support profiling areas and analyze the entire application. The Code to Profile pane is visible only if one of the following profilers is currently selected. These profilers support either routine-, or line-level profiling areas, or both:

If you change the current profiler to one of the profilers that supports stack areas, then the routine- and line-level profiling areas will be used as stack areas and will be shown in the Collect Stack Information pane. Similarly, when you switch back to one of the profilers mentioned above, stack areas will be treated as profiling areas of the routine- and line-level types.

Predefined Areas

The Code to Profile pane contains a number of predefined profiling areas. You can use them to easily include large code portions in profiling tasks:

All Project Modules - AQTime will profile all the routines that belong to modules added to the current AQTime project modules (except for the routines added to excluding areas or excluded by the Ignore Files or Ignore Routines dialog).
Entire .NET Code - AQTime will profile all managed (.NET) functions even if they do not belong to the modules added to the Setup panel.
Entire Script Code - AQTime will profile all the script routines that are executed within the host application launched by AQTime.
Entire Java Code - AQTime will profile all the functions executed by the Java Virtual Machine.

Note:

If you select either the Entire .NET Code, Entire Script Code or Entire Java Code area, AQTime will profile even those .NET, script or Java functions that were added to profiling areas of the excluding type. To exclude code from profiling in this case, use the Ignore Files and Ignore Routines dialogs. For complete information on specifying code portions for profiling, see Controlling What to Profile.

Custom Profiling Areas

In addition to using predefined profiling areas, you can also create and use custom areas to specify routines to be profiled or ignored.

Each custom area can contain individual routines, as well as larger code elements like classes, namespaces, files, units and modules. When you add a class, unit or module to an area, this means that the area contains all the routines defined in the class, unit or module.

To add a custom area to your project

Right-click somewhere within the Code to Profile pane and select Add Stack Area from the context menu.
In the subsequent Add Profiling Area dialog, you specify the area name and type: including (default) or excluding.

If the selected profiler supports line-level analysis, then for including areas, you can also select the Collect info about lines check box in the dialog. In this case, the area becomes a line-level area, that is, AQTime will profile the routines in it at line level: it will measure line execution time, gather coverage info for lines and so on. See About Profiling Levels.

To modify area settings

Right-click the desired area in the Code to Profile pane and choose Edit Profiling Area from the context menu.
Change the area settings in the subsequent Edit Area dialog.

To add code elements to an area

Drag the desired code element (like a routine, class, unit or module) from the Modules pane to the area.

-- or --

Right-click the desired elements in the Modules pane and select the target area from the list in the Add Selected to ... submenu.

An element can belong to as many profiling areas as you wish.

If an element is checked in an excluding stack area, this will override all the checks in including stack areas.

To remove an area

Right-click the desired area and select Remove from the context menu.