Page Contents:

• Compatibility
  • Supported Platforms and System Requirements
  • Profiling Managed Extensions in C++ Programs
  • Unpacking into an Existing Project Directory
  • Optimizations Lost During Profiling
  
  
• Usage
  • Not Viewing Unmanaged DLLs Executed Under the Profiled Process
  • Viewing Unmanaged DLLs Executed Under the Profiled Process
  • Profiling ASP.NET* Applications
  • Profiling COM+ .NET* Services
  • Profiling COM+ .NET* Services on Windows* Server 2003*
  • Profiling .NET* Programs Invoked Via a Script

• Supported Platforms and System Requirements
  Which versions of the Microsoft .NET Framework* does the VTune™ Performance Analyzer 7.1 support?
  IA-32 systems support versions 1.0 and 1.1 of the .NET Framework*. The VTune analyzer does not support profiling for the .NET Framework* on Itanium®-based systems
  
  
• Profiling Managed Extensions in C++ Programs
  Can the VTune analyzer profile Managed Extensions in C++ programs?
  Yes. This includes .NET* DLLs, native IA-32 DLLs, and mixed DLLs that contain both managed and unmanaged code.
  
  
• Unpacking into an Existing Project Directory
  I cannot unpack a project into an existing project directory?
  The VTune analyzer can't unpack a project (associated with pre-jitted files) into an existing project directory. So you may face this problem if you profiled a .NET* program with a few pre-jitted .NET* modules, or .NET* system modules. The work around is to unpack into a new project directory.
  
  
• Optimizations Lost During Profiling
  My .NET* application seems to lose all optimizations when being profiled?
  If you are profiling your application using .NET Framework* version 1.0.3705, this is probably true. To get most optimizations back, you need to create an INI file with the same base name as the executable - for example, create app-name.ini in the same directory where your executable, app-name.exe, resides. The file should contain the following two lines:

  [.NET Framework Debugging Control]
  
  AllowOptimize=1

• Not Viewing Unmanaged DLLs Executed Under the Profiled Process
  How do I get a call graph of my .NET* application only, without all the native DLLs that execute under the profiled process?
  Use the call graph wizard, and select .NET Profiling. Specify the relevant information about your application in the various wizard windows. The last window allows you to choose between call graph with .NET classes only, and a complete call graph that includes both .NET and native calls. The default is .NET classes only.
  
  
• Viewing Unmanaged DLLs Executed Under the Profiled Process
  How do I get a call graph of my .NET* program including all the native DLLs that execute under the profiled process?
  Use the call graph wizard, and select .NET Profiling. Specify all the relevant information about your application in the various wizard steps. The last step enables you to choose between call graph with .NET classes only, and a complete call graph that includes both .NET and native calls. The default is .NET classes only. Select All .NET classes and all native modules to get both .NET and native code call graph data.
  
  
• Profiling ASP.NET* Applications
  How can I profile my ASP.NET* application?
  The sampling and call graph wizards guide you through the various stages required to profile an ASP.NET* application.
  
  It is recommended that you shut down all clients of all Internet Services before invoking an ASP.NET* profiling session, and before stopping the profiling session. The VTune analyzer restarts IIS as part of the profiling startup and termination process. This might have unpredictable effects on client applications, including system crashes.
  
  
• Profiling COM+ .NET* Services
  How can I profile my COM+ .NET* service?
  The sampling and call graph wizards guide you through the various stages required to profile a COM+ .NET* service. You need to execute your COM+ .NET* service on the machine where you intend to profile it, at least once before profiling. This will ensure all COM+ services are properly registered and displayed for selection in the call graph wizard.
  
  Call Graph profiling of COM+ .NET* services is not supported on the Windows* Server 2003*.
  
  Currently, profiling COM+ .NET applications is not supported on 32-bit Intel processors with Intel EM64T running 64-bit operating systems and Itanium®-based systems.
  
  Please refer to the COM+ profiling white paper at http://www.intel.com/software/products/vtune/vpa/callgraph.pdf.
  
  
• Profiling COM+ .NET* Services on Windows* Server 2003*
  How can I profile my COM+ .NET* service on Windows* Server 2003?
  Call Graph profiling of COM+ .NET* services is not supported on the Windows* Server 2003*.
  
  For sampling you need to change the identity to This User, and set the user name and password. Follow these steps to get this done:
  1. Open Control Panel » Administrative Tools » Component Services.
  2. In the Component Services dialog, on the left side, open Component Services » Computers » My Computer » COM+ Applications.
  3. Select your COM+ .NET* service.
  4. Right-click on it and select Properties.
  5. Go to the Identity tab. Interactive user should be selected by default.
  6. Change the account to This user and input the user name and password into the corresponding fields.
  7. Click Apply to save changes.
  
  
• Profiling .NET* Programs Invoked Via a Script
  How can I profile a .NET* program invoked via a script?
  The call graph and sampling wizards enable you to specify a script that invokes your application.

This applies to:

Intel® VTune™ Performance Analyzer for Windows*