dotTrace 2016.1 Help

Appendix A. Integrating dotTrace with Typemock Isolator

dotTrace integrates with Typemock Isolator, so you can not only test your code, but also investigate performance problems.

Before starting, make sure that appropriate versions of tools are installed:

  • JetBrains dotTrace 4.5.1 or higher
  • Typemock Isolator 6.2.5

To integrate dotTrace with Typemock Isolator

  1. Launch Typemock.Configuration.exe. The Typemock Isolator Configuration dialog box opens.
  2. Select the Show only available profilers check box to narrow down the list of profiling and coverage tools.
  3. Find and click the appropriate version of dotTrace.
  4. Click Link with Typemock Isolator and close the dialog.

Transparent Integration Concepts

Transparent integration mechanism allows running any 3rd party core before dotTrace profiler core. The 3rd party core is responsible for loading and configuring dotTrace profiler core. It is guaranteed that dotTrace profiler core is deployed and registered before profiling.

To be sure that dotTrace and 3rd party utility work correctly together, make some additional checks.

At least one of the following registry keys should exist:

  • HKEY_CURRENT_USER\SOFTWARE\JetBrains\Profiler\TransparentIntegration
  • HKEY_LOCAL_MACHINE\SOFTWARE\JetBrains\Profiler\TransparentIntegration (32-bit or 64-bit)

And should contain one or more values:

  • SamplingPerformanceProfiler = <3rd party CLSID>
  • TracingPerformanceProfiler = <3rd party CLSID>
  • TracingInjectPerformanceProfiler = <3rd party CLSID>
Each of these values should be of REG_SZ type and should not be empty.

One of these locations should contain JETBRAINS_PROFILER_CORE_GUID, so that the 3rd party core could load the dotTrace profiler core.

  • HKEY_CURRENT_USER\SOFTWARE\JetBrains\Profiler\Pid_XXX, where XXX is a decimal process id
  • HKEY_LOCAL_MACHINE\SOFTWARE\JetBrains\Profiler\Pid_XXX, where XXX is a decimal process id
  • Environment variables
  • HKEY_LOCAL_MACHINE\SOFTWARE\JetBrains\Profiler\Global
The order in which the 3rd party utility traverses these locations in search of JETBRAINS_PROFILER_CORE_GUID is very important. If the order is not followed, integration might not work properly.

See Also

Last modified: 19 August 2016