Sunday, December 07, 2008

Code Analysis Invalid Settings Error When Invoked from within VSTS

This issue plagued me for several hours today so I'm posting my resolution. Executing Code Analysis from within Visual Studio Team System - Team Suite kept reporting:
"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.
Microsoft (R) FxCop Command-Line Tool, Version 1.36 (9.0.21022.8)
Copyright (C) 2007 Microsoft Corporation. All rights reserved.
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).

After restarting VSTS, I received a successful code analysis result. Whew...back to my demo preparation.


David Kean said...

I already replied on the thread, but I'll reply here as well.
This is most likely caused by the VS2008 Service Pack 1 not correctly being installed. Try reinstalling it.

Jeff Hunsaker said...

@David, Appreciate the suggestion. I'll give that a shot. Cleaner than my solution.

Anonymous said...

The was the only way I was able to resolve this:

I added a environment variable called: CodeAnalysisPath pointing to:
C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v9.0\CodeAnalysis

whittet said...

Building in VS2010 resulted in the CA0059 error on my machine. Copying the Visual Studio 2010 FxCop folder to the VS 2008 FxCop folder resolved the issue.