This topic describes the changes made to AQTime 8.0. For information on the changes made to other versions of the product, see Version History.
Support for Windows 8 and Windows Server 2012. You can now run AQTime and optimize your applications on the latest version of Microsoft operating systems: Windows 8 and Windows Server 2012.
AQTime currently supports profiling ordinary Windows applications. Metro UI applications are not supported.
.NET Framework 4.5 support. You can now use AQTime’s profilers to analyze and optimize .NET-connected applications created for Microsoft .NET Framework 4.5.
Visual Studio 2012 support. AQTime 8 includes full support for Microsoft Visual Studio 2012. This means that --
You can profile managed and unmanaged desktop and Web applications created in Microsoft Visual Studio 2012.
AQTime integrates into Visual Studio 2012 user interface enabling you to optimize your code directly without leaving the IDE.
You can run AQTime projects as part of team builds that are created and run with Visual Studio 2012.
New Cyclomatic Complexity metric in the Static Analysis results. The Static Analysis profiler now measures and reports a new metric for your code - cyclomatic complexity. It lets you estimate the algorithmic complexity of your routines. Routines with high complexity may need reviewing. You can examine their source code and decide if they require rewriting.
New profiling mode for the Light Coverage profiler. The Light Coverage profiler now supports two profiling modes: Profile code in debuggee process, which corresponds to the profiler’s behavior in AQTime 7 and earlier, and Profile code in any process, which is new and which was developed specially for profiling modules that can be used in various processes. Using the new mode you can profile modules that are loaded in processes which were not launched from AQTime and to which you may be unable to attach. A typical example of these modules are DLLs that implement hook functionality and that can be injected into an arbitrary process. For more information on using the new mode, see Profiling DLLs That Can Be Loaded in Various Processes.
New settings for collecting class stack data. Now you can specify which modules, classes and routines will be included in the call stack data collected by the Allocation, Resource, Reference Count and Failure Emulator profilers. In earlier versions of AQTime, call stacks contain calls to your application’s routines as well as calls to third-party and system functions. In certain cases, the latter increased the call stack size and made the call stack data difficult to analyze. The new functionality helps you hide unnecessary calls from the call stack and concentrate on the code you are interested in.
You specify the new settings by using stack areas. These are collections of modules, units, classes or individual routines which AQTime should include in the collected stacks. Stack areas are very similar to profiling areas but they are not used to specify what to profile. They specify what to include in the reported stacks.
You create and configure stack areas in the new Collect Stack Information section of the Setup panel. This section is available only for the Allocation, Resource, Reference Count and Failure Emulator profilers.
One installation package for 32-bit and 64-bit operating systems. Earlier versions of AQTime used two installation packages: AQTime x86 for 32-bit operating systems and AQTime x64 for 64-bit systems. AQTime version 8 uses only one package that includes both 32- and 64-bit modules. This simplifies the installation and decreases the overall size of AQTime’s installation package.
Improved command-line automation abilities. The AQTime executable (AQtime.exe) now has exit codes that allow you to determine the last profiling result. AQTime uses these new codes if you specify a new
/nonzeroexitcode argument in the command line. See AQTime Command Line and AQTime Exit Codes.
The Force Garbage Collection menu and toolbar item now supports .NET 4.x applications. In earlier versions, it was disabled when you profiled these applications.
Predefined profiling areas have been changed a little. The Full Check area has been renamed to All Project Modules, and we have removed the word Profile from other area names to make the names shorter.
A number of bugs have been fixed.