Partager via

Building an Application That Supports Remote Call Profiler Data Collection

  • Article

To instrument an application for Remote Call Profiler, you can set an environment variable that specifies the type of profiling probe to insert into the application, and then build the application. You can then use Remote Call Profiler to collect data while the instrumented application runs.

To build an application that supports Remote Call Profiler data collection

  1. Open a command prompt build window.

    In the PB IDE, to open a command prompt build window, from the Build menu, choose Open Build Release Directory.

  2. To instrument the application with CallCAP probes, at the command prompt, type set WINCECALLCAP=1.

    - or -

    To instrument the application with FastCAP probes, at the command prompt, type set WINCEFASTCAP=1.

    Note   FastCAP instrumentation is not supported on x86 microprocessors.

    For information about the characteristics of CallCAP and FastCAP probes, see Characteristics of FastCAP and CallCAP Probes.

  3. At the command prompt, type set WINCEREL=1.

  4. Navigate to the directory that contains the sources file for the application that you want to instrument.

  5. At the command prompt, type build -c.

    At the end of the build process, the build window displays a BUILD: Done message, followed by a message that reports the number of files compiled.

    The file name and file name extension of the built application are determined by the values that you specified in the sources file in the directory containing the source code for the application. For more information about sources files, see Sources File.

See Also

Remote Call Profiler Instrumented Module Building | How to Use Remote Call Profiler to Find Performance Problems | Creating a Command Prompt Build Window | Code Profiling

 Last updated on Friday, October 08, 2004

© 1992-2003 Microsoft Corporation. All rights reserved.