Create portable profiling data files from the command line

  • Article

Applies to: yesVisual Studio noVisual Studio for Mac

Note

This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

To make sharing of profiling data easier, you can use the VSPerfReport command-line tool to embed the symbols for a profiling run into the .vsp file.

You can also create a pre-analyzed profiling data (.vsps) file that is smaller and is quicker to load in the IDE.

Note

Make sure the symbol (.pdb) files are available to VSPerfReport. For more information, see How to: Specify symbol file locations from the command line.

For information about the path to VSReport, see Specify the path to command-line tools.

The profiling data in a .vsps file cannot be filtered.

To embed the symbols for a profiling run into a profiling data (.vsp) file

  • At a command prompt window, type the following command:

    <Path>VSPerfReport <VSP File> /PackSymbols

    By default, the .vsps file is named with the base name of the .vsp file. You can specify an alternative name by using the Output option.

To create a summary profiling data file

  • At a command prompt window, type the following command:

    <Path>VSPerfReport <VSP File> /SummaryFile [/Output:<File Name>]

    By default, the .vsps file is named with the base name of the .vsp file. You can specify an alternative name by using the Output option.