none
TFS 2008 SP1 Still "Chatty"?

    Question

  •  

    I thought I read somewhere that SP1 was going to get rid of a majority of the build steps like "CopyOutputToDirectory", etc during compilation.

     

    I installed and it's still pretty chatty.  Am I missing something?

    Saturday, August 16, 2008 4:05 PM

Answers

  • There are two distinct issues mentioned in this thread:

    (1) Noisy build logs (i.e. the text files generated during the course of the build).
    (2) Noisy build reports (i.e. the GUI that shows up within Visual Studio for a particular Build).

    The first issue is easily solvable by modifying the verbosity of MSBuild.  With the change from MSBuild 2.0 to MSBuild 3.5, the MSBuild team modified the default verbosity of their file logger, which is used by Team Build to generate our build logs, from Normal to Diagnostic.  To dial down the verbosity, just add "/flp:verbosity= normal" to your TfsBuild.rsp file - see my blog post at http://blogs.msdn.com/aaronhallberg/archive/2007/05/03/tfsbuild-rsp-and-logging-verbosity-in-orcas.aspx for more details.

    The second issue is, unfortunately, more problematic.  As mentioned in my blog post at http://blogs.msdn.com/aaronhallberg/archive/2008/05/05/orcas-sp1-tfs-build-changes.aspx, we attempted to fix this issue in TFS 2008 SP1 with the addition of the TargetsNotLogged property.  Unfortunately, we only partially fixed the problem - the mechanism we used to communicate the TargetsNotLogged property to our logger and thereby skip the logging of particular targets only worked the first time a particular project-to-project reference was evaluated.  So, for example, if a project is referenced by 10 other projects SP1 would take you from 10*3 extraneous build steps to 9*3 extraneous build steps. 

    A more comprehensive fix is in the works as a hotfix, but I do not believe it has been officially released just yet.  Keep an eye on my blog (http://blogs.msdn.com/aaronhallberg) and I'll be sure to post something once the fix is available.

    -Aaron
    http://blogs.msdn.com/aaronhallberg
    Wednesday, December 31, 2008 4:11 PM
    Moderator

All replies

  • You are the second person to report the problem. We are investigating and will let you know something as soon as possible.

     

    Thanks,

    Jason

     

    Monday, August 18, 2008 3:06 PM
  •  

    FYI: this is happening on all three of our build servers.  All are evals upgraded to RTM later on.
    Monday, August 18, 2008 5:14 PM
  • Any thoughts on this yet?  Do you need any logs?  Access to any servers?

     

    Saturday, August 23, 2008 1:27 AM
  • We are also seeing this problem on our build server. After installing SP1 on the build server, I can see the TargetsNotLogged property is present in the team build targets file, and I've confirmed that it is populated as expected during the build, but the GetTargetPath, GetNativeManifest, and GetCopyToOutputDirectoryItems targets are still clogging up my build steps.

     

    Any idea on why this is still happening?

     

    Glenn Burnside

    Dell, Inc.

    Thursday, August 28, 2008 3:56 AM
  • We are still investigating this problem with the MSBuild team. I will let you know as soon as we have any news and hopefully a workaround.

     

    Thanks,

    Jason

     

    Tuesday, September 02, 2008 12:54 PM
  • Anything about

    how to reduce the Noise of targets in the BuildLog file?

    pls let me know.

    Friday, September 05, 2008 5:50 PM
  • Hi All,

     

    I found this article http://blogs.msdn.com/aaronhallberg/archive/2008/05/05/orcas-sp1-tfs-build-changes.aspx by Aaron Hallberg and just found that in TFS 2008 SP1 thye have included such thing in which we can reduce the noise in our build log.

     

    So i downloaded SP1 for TFS2008 and have installed it. But this does`t seems to be working...

    It still shows all these targets in Build Log. I checked the Martgets file under MSBUILD\Windows\TeamBuild.  here the file is updated and i can see the new version of the file being updated and this target is actually there , But build log is still having the targets populated which should not be there after we install the Sp1.

     

    is there anything we need to do in out tfsbuild.proj (i dont think so).

     

    Pls anyone has tried this new feature let me know.

     

     

     

    Monday, September 08, 2008 6:37 PM
  • Did you install the Visual Studio SP1 to the Build machine? Make sure the SP1 is installed on the build machine and the AT if you are in a mutli-Tier TFS environment. In addition, you may still need to use Aaron suggestion at http://blogs.msdn.com/aaronhallberg/archive/2008/05/05/orcas-sp1-tfs-build-changes.aspx for reducing the noise.

     

    Wednesday, September 10, 2008 7:42 PM
  • Hi,

    Yes i Have VS 2008 SP1 installed, below is the list, and i am following the suggestins from Aaron blog. Still no change.?

    -----------------------------------------------------------------------------------------------------------------

     

    Microsoft Visual Studio 2008
    Version 9.0.21022.8 RTM
    Microsoft .NET Framework
    Version 3.5

    Installed Edition: Enterprise

    Microsoft Visual Basic 2008  

    Microsoft Visual Basic 2008

    Microsoft Visual C# 2008  
    Microsoft Visual C# 2008

    Microsoft Visual C++ 2008  

    Microsoft Visual C++ 2008

    Microsoft Visual Studio 2008 Team Explorer  

    Microsoft Visual Studio 2008 Team Explorer
    Version 9.0.30729.1

    Microsoft Visual Studio 2008 Tools for Office  
    Microsoft Visual Studio 2008 Tools for Office

    Microsoft Visual Studio Team System 2008 Development Edition  

    Microsoft Visual Web Developer 2008  
    Crystal Reports   
    Crystal Reports Basic for Visual Studio 2008


    Hotfix for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU (KB946260)   KB946260
    This hotfix is for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/946260.

    Hotfix for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU (KB946458)   KB946458
    This hotfix is for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/946458.

    Hotfix for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU (KB947171)   KB947171
    This hotfix is for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/947171.

    Hotfix for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU (KB947180)   KB947180
    This hotfix is for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/947180.

    Hotfix for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU (KB948816)   KB948816
    This hotfix is for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU.
    If you later install a more recent service pack, this hotfix will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/948816.

    Microsoft Visual Studio 2008 Team Foundation Server Build - ENU Service Pack 1 (KB949786)   KB949786
    This service pack is for Microsoft Visual Studio 2008 Team Foundation Server Build - ENU.
    If you later install a more recent service pack, this service pack will be uninstalled automatically.
    For more information, visit http://support.microsoft.com/kb/949786.

    Windows Installer XML   Version 3.0
    Votive - Windows Installer XML (WiX) Toolset, Version 3.0.4318.0
    Copyright © Microsoft Corporation. All rights reserved.

     

     

    This is wht you meant right?

     

    Thursday, September 11, 2008 2:53 PM
  • Hi!

     

     

    I have installed the service packs today. My buildlog is just as messy as beforeSad

     

    Has anyone found a solution?

     

     

    Regards,

    Kai

     

     

     

     

     

    Monday, September 15, 2008 5:25 PM
  •  
    I am seeing this problem also and my list of details is so big that I can't even scroll to the bottom of the Build Steps anymore.

    Has anyone found a solution for this  yet?

    Thanks
    -- Steven
    Friday, October 10, 2008 3:30 PM
  • Seeing this on all our build servers also. Confirmed VS2008 SP1 and TFS2008 SP1 installed on all build servers, TFS server, and development workstations. Confirmed presence of TargetsNotLogged in .targets file on build servers.
    Tuesday, October 14, 2008 4:25 AM
  • Been monitoring this thread since our upgrade as well, and seeing the same issue over here. Went through the same checklist, and even verified that TargetsNotLogged does get set properly (defaults to: GetTargetPath;GetNativeManifest;GetCopyToOutputDirectoryItems) during a build by temporarily using diagnostics (/flp:v=diag /v:diag). Both the diagnostic and normal builds are still noisy.

    Any ideas?
    Friday, October 17, 2008 5:38 PM
  • There are two distinct issues mentioned in this thread:

    (1) Noisy build logs (i.e. the text files generated during the course of the build).
    (2) Noisy build reports (i.e. the GUI that shows up within Visual Studio for a particular Build).

    The first issue is easily solvable by modifying the verbosity of MSBuild.  With the change from MSBuild 2.0 to MSBuild 3.5, the MSBuild team modified the default verbosity of their file logger, which is used by Team Build to generate our build logs, from Normal to Diagnostic.  To dial down the verbosity, just add "/flp:verbosity= normal" to your TfsBuild.rsp file - see my blog post at http://blogs.msdn.com/aaronhallberg/archive/2007/05/03/tfsbuild-rsp-and-logging-verbosity-in-orcas.aspx for more details.

    The second issue is, unfortunately, more problematic.  As mentioned in my blog post at http://blogs.msdn.com/aaronhallberg/archive/2008/05/05/orcas-sp1-tfs-build-changes.aspx, we attempted to fix this issue in TFS 2008 SP1 with the addition of the TargetsNotLogged property.  Unfortunately, we only partially fixed the problem - the mechanism we used to communicate the TargetsNotLogged property to our logger and thereby skip the logging of particular targets only worked the first time a particular project-to-project reference was evaluated.  So, for example, if a project is referenced by 10 other projects SP1 would take you from 10*3 extraneous build steps to 9*3 extraneous build steps. 

    A more comprehensive fix is in the works as a hotfix, but I do not believe it has been officially released just yet.  Keep an eye on my blog (http://blogs.msdn.com/aaronhallberg) and I'll be sure to post something once the fix is available.

    -Aaron
    http://blogs.msdn.com/aaronhallberg
    Wednesday, December 31, 2008 4:11 PM
    Moderator
  • A hotfix that solves the remaining portion of this issue is finally available here: http://code.msdn.microsoft.com/KB958845.  You'll need to have SP1 installed on your build machine before applying the hotfix.


    http://blogs.msdn.com/aaronhallberg
    Friday, January 30, 2009 4:17 PM
    Moderator
  • I have VS2008 + SP1 installed but when running this update I get the message "None of the products that are addressed by this software update are installed on this computer." What condition is being evaluated to determine if the update applies?

    -Aidan
    Wednesday, September 23, 2009 4:53 PM
  • I have VS2008 + SP1 installed but when running this update I get the message "None of the products that are addressed by this software update are installed on this computer." What condition is being evaluated to determine if the update applies?

    -Aidan

     Found an answer to this problem Aidan ?
    Friday, August 06, 2010 2:35 PM