Menu
Home | Manual | Donations

Manual

The MSBuild profiler is pretty easy to use. The tool will hopefully be integrated in other tools at a later time, but until then, you will need to start it manually from the command prompt.

Profiling

To profile a build, you will need to install the MSBuild Profiler and choose one of two ways of running the profiler. The first option is to run an MSBuild script and letting the profiler application starting up after the build has been completed. This approach is great for profiling the performance of a script on you local machine. The other approach is not run the profiler on a scriptet form. This is great to save snapshots for later viewing at a buildserver or other scriptet environment.

Manual Profiling

In order to profile a build file manually, execute your MSBuild script with the following parameters:

MSBuild.exe mybuildfile.proj /t:mytarget /l:MSBuildProfileLogger,MSBuildProfiler,Version=1.0.1.0,Culture=neutral,PublicKeyToken=09544254e89d148c


Where mybuildfile.proj is the name of your buildfile (or not specified if the current directory only contains one buildfile) and mytarget is the name of the target(s) you want to profile.

Scriptet Profiling

In order to profile a build file in a scriptet way, add the following parameters to your script executing MSBuild:

MSBuild.exe mybuildfile.proj /t:mytarget /l:MSBuildProfileFileLogger,MSBuildProfiler,Version=1.0.1.0,Culture=neutral,PublicKeyToken=09544254e89d148c;file=my.snapshot


Where mybuildfile.proj is the name of your buildfile, mytarget is the name of the target(s) you want to profile and file specifies the filename of the saved snapshot. You can avoid specifying the file parameter. This will just create a build.snapshot file.

Last edited Oct 23, 2007 at 12:18 AM by ThomasArdal, version 4

Comments

No comments yet.