"Invalid settings passed to CodeAnalysis task. See output window for details."
MSBuild is unable to locate the correct binaries to perform Code Analysis on managed binaries. Make sure that either Visual Studio Team System 2008 Development Edition or Visual Studio Team System 2008 Team Suite is installed with the Code Analysis feature. If MSBuild is being run from within the "Visual Studio Command Prompt", specify the path to your analysis binaries by setting the FXCOPDIR environment variable.At first, after a search, I thought it was an Environment Variable issue regarding the path to FxCopCmd.exe. Very helpful post here. However, after adding the Environment Variable FxCopDir, I was closer but still getting an error.
Finally, I took the FxCopCmd.exe command line string into a command window and executed. It came back with:
Switch '/targetframeworkversion' is an unknown switch.Ah ha. Now we're getting somewhere. Hypothesizing this was an old version of FxCop which didn't understand target frameworks, I downloaded the latest (which provides support for .Net 3.5 SP1) and installed it to %ProgramFiles%\Microsoft Visual Studio 9.0\Team Tools\Static Analysis Tools\FxCop (making a backup copy of the directory first).
Microsoft (R) FxCop Command-Line Tool, Version 1.36 (9.0.21022.8)
Copyright (C) 2007 Microsoft Corporation. All rights reserved.
After restarting VSTS, I received a successful code analysis result. Whew...back to my demo preparation.