Strange Code Analysis Problem About TFS 2010 Build

StackOverflow https://stackoverflow.com/questions/4668979

Question

I have got strange problems in the last few days. Today's strange problem is about Code Analysis and TFS 2010 Builds.

After we had upgraded our TFS from 2008 to 2010, we then upgraded our solutions from Visual Studio 2008 to 2010. There were no errors while upgrading, but we saw strange things about code analysis.

Shortly the problem is, FxCop results differ by running automatically from tfs 2010 build or running manually from command prompt. Even though they are both using the same command parameters and values.

For example i̇f i run FxCop in the TFS build, I get 7 errors, but i̇f I run FxCop by command prompt using the command I see in the build log, I get 133 errors.

What could cause these differences?

Was it helpful?

Solution 2

I solved this problem.

It was about CustomDictionary path.

I deleted FXCop\CustomDictionary.xml for test and forget. I replaced CustomDictionary and everything became normal.

OTHER TIPS

Have you verified that your VS and command line analysis runs are using the same rule sets?

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top