Is there an easy way to log the amount of time that Visual Studio 2010 spends on building?

We would like to automatically record the time that we spend on the construction of our project every day, during its development. Build can be initiated by pressing f5 or by running our n-unit tests using TestDriven.Net. We want the whole assembly time to be built not only for one or two projects. We want to do this in order to compare the performance impact of a slow PC versus a fast PC. Any ideas?

Update: I researched the MSBuild loggers. It seems like this might work, but I can't figure out how to send parameters to MSBuild when we build f5 from VS.

+6
visual-studio-2010 msbuild
source share
4 answers

VSCommands for Visual Studio 2010 and 2012 can be obtained from Gallery Visual Studio can create detailed assembly statistics in the output window after the assembly is completed:

enter image description here

+5
source share

Tools + Options, projects and solutions, assembly and launch. Change the value of the multi-page build version of the MSBuild project to Normal. At the end of the build, you get the Time Elapsed dimension. You can set this parameter to 11 to get a detailed analysis. The build log entry is automatically saved in the buildlog.htm file in the project build directory.

Equivalent command line option: / verbosity: normal (/ v: n). You can get the output registered to the redirected file or the / fileLogger (/ fl) option. Type msbuild /? To get a summary of these options, there are a few more obscure ways to register.

+3
source share

In the project output directory there is a project_name.log file with a line

"Elapsed time 00: 00: 00.00"

You can analyze this

0
source share

You can use Tools | Options | Projects and Solutions | Project Settings VC ++ | Build Timing to determine if this copy of Visual Studio includes synchronization in the release of the VC ++ assembly.

But this time and time elapsed with @Martin appears in the Visual Studio output window when you create F5 and in the console when you execute line assemblies.

It sounds like you really want to collect assembly time for several assemblies in one place. One place to look can be MSBuild Loggers .

0
source share

All Articles