http://blogs.msdn.com/aaronhallberg/archive/2007/05/03/tfsbuild-rsp-and-logging-verbosity-in-orcas.aspxIn the 2.0 .NET Framework, MSBuild's default verbosity for its FileLogger was "normal". As such, if you needed diagnostic logging information in a Team Build build (e.g. for debugging an issue with the build process) you needed to add the following toenCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/aaronhallberg/archive/2007/05/03/tfsbuild-rsp-and-logging-verbosity-in-orcas.aspx#2480987Tue, 08 May 2007 18:03:24 GMT91d46819-8472-40ad-a661-2c78acb4018c:2480987Team System News<p>Brian Harry on All Orcas Beta 1 downloads are now available. Tan on Resuming Conflict Resolution in Team...</p> http://blogs.msdn.com/aaronhallberg/archive/2007/05/03/tfsbuild-rsp-and-logging-verbosity-in-orcas.aspx#5244096Tue, 02 Oct 2007 18:38:11 GMT91d46819-8472-40ad-a661-2c78acb4018c:5244096Aaron Hallberg<p>A while back I had a post on the modified command-line options for file logging in MSBuild in the 3.5</p> http://blogs.msdn.com/aaronhallberg/archive/2007/05/03/tfsbuild-rsp-and-logging-verbosity-in-orcas.aspx#8108839Sat, 08 Mar 2008 05:11:38 GMT91d46819-8472-40ad-a661-2c78acb4018c:8108839mikeycooper<p>Aaron, this solved my problem with buildlog.txt being enormous after a team build. &nbsp;Thanks! &nbsp;I still have an issue where the number of build steps generated for multiple solutions has blown out from several hundred in TFS 2005 to 3500+ in TFS 2008. &nbsp;Do you know if there's some way yet to turn down the verbosity of what gets logged as a &nbsp;build step?</p> http://blogs.msdn.com/aaronhallberg/archive/2007/05/03/tfsbuild-rsp-and-logging-verbosity-in-orcas.aspx#8364589Mon, 07 Apr 2008 10:02:12 GMT91d46819-8472-40ad-a661-2c78acb4018c:8364589Pierre-Emmanuel Dautreppe<p>TFS : Control the verbosity of the logging during the build</p>