Child pages
  • How to profile .NET Compact Framework applications
Skip to end of metadata
Go to start of metadata


Host computer software

  1. ActiveSync (for Windows XP, Windows Server 2003) / Windows Mobile Device Center (Windows Vista / Windows Server 2008 / Windows 7)
  2. .NET Compact Framework 2.0 SP1
  3. .NET Compact Framework 3.5 SP1
  4. Visual Studio 2005 SP1 or higher
  5. Windows Mobile 6 SDK
  6. PowerToys for .NET Compact Framework 3.5 (or higher)

Mobile device software

  1. .NET Compact Framework 3.5 SP1 (NETCFv35.wm.armv4i). If you are running from VS, it is installed automatically. If it is not installed, you can get it from "C:\Program Files (x86)\Microsoft.NET\SDK\CompactFramework\v3.5\WindowsCE"
  2. Your Windows Mobile application

    It may be necessary to place a config file to the application folder. The config file should follow the naming pattern <ApplicationName>.exe.config and contain the following data:

    where version is your .NET Compact Framework version.


  1. Connect your device (this is optional if you're going to use an emulator)
  2. Start dotTrace Performance.
  3. Select Profile | Smart Device Application.
  4. Add a new host. Select your device from the list.
  5. Specify the path to the application at the device.
  6. Click OK. The selected application will start at the device. Keep it running until you're ready to get a snapshot. Grab a snapshot, and you're done.

Known Issues

Invalid Index error in tracing mode

Most likelу the error is caused by a known bug in .NET Compact Framework 3.5.

The best workaround is switching to Sampling profiling.

If the application being profiled in tracing mode throws an exception from a method, property etc., the profiler doesn't anymore get notified about certain framework events and fails with the "Invalid Index" error.

Here is an example of valid code:

The example below will cause the "Invalid Index" error:

Can't connect to host. Unsupported instruction set

Most likely you are trying to profile a Windows CE 4.x application, which is not supported by dotTrace 4 Performance.

The operation has been cancelled

There are two known possible reasons:

  1. Some devices display a confirmation dialog box. If you don't explicitly agree, you get this error.
  2. There's a 1-minute timeout for copying profile core dll and profiler core pdb to Windows folder in the device. You might get this error if data transfer speed is low.

How to diagnose

Start profiling and navigate to Windows folder in the device. Search for JetBrains.Profiler.Core.WinCE.YourProcessorType.dll and JetBrains.Profiler.Core.WinCE.YourProcessorType.pdb.

Search for these files in dotTrace bin folder (C:\Program Files (x86)\JetBrains\dotTrace\v4.0\Bin). If the files in the two locations differ in size, data transfer rate is too low.

Note that dotTrace Performance release builds only include the dll file. The pdb file is only included with nightly builds.

If you're experiencing this issue with a nightly build, try deleting the pdb file from dotTrace installation directory.

Missing dll file JetBrains.Profiler.Core.WinCE.ARMV4I_fp.dll

This issue was fixed in dotTrace Performance 4.0.1. Please download the latest product version.

  • No labels