Using the Profiling Tools From the Command-Line
You can use the command-line tools of Visual Studio Profiling Tools to profile applications at the command prompt and to automate profiling by using batch files and scripting. You can also generate report files at a command prompt. You can use the lightweight stand-alone profiler to collect data on computers that do not have Visual Studio installed.
Note
Enhanced security features in Windows 8 and Windows Server 2012 required significant changes in the way the Visual Studio profiler collects data on these platforms. Windows Store apps also require new collection techniques. See Profiling Windows 8 and Windows Server 2012 applications.
Common Tasks
Task |
Related Content |
|---|---|
Set the location of symbols: To display the names of functions and parameters, the profiler must have access to the symbol (.pdb) files of the profiled binaries. These files should include the symbol files for the Microsoft operating system and applications that you want to view in your analysis. You can use the public Microsoft symbol server to make sure that you have the correct .pdb files for the Microsoft binaries. |
|
Profile your application: The command-line tools and options that you use to profile a target application depend on the type of the application, the profiling method, and whether the target is a managed or native application. |
|
Create .xml and .csv reports: Profiling at the command prompt creates data files that can be viewed in the interface for Visual Studio. You can also generate .xml or comma-separated value (.csv) files of the data by using the VSPerfReport command-line tool. |
|
Profile code on computers without Visual Studio: You can use the Profiling Tools stand-alone profiler to collect data for applications on computers that do not have Visual Studio installed. |
Reference
Command-Line Profiling Tools Reference