3
Vote

Building source causes hard error CA0001 -- exception thrown by FxCop

description

Building this set of source files with code analysis turned on causes a hard error whose message says:
Error 13 CA0001 : Rule=Microsoft.Naming#CA1725, Target=Microsoft.VisualStudio.Project.Automation.OAReferenceBase`1.#get_Extender(System.String) : Object reference not set to an instance of an object. MPFProj
 
Suppressing the rule in source or in the global suppressions file does not work around this error, but turning off this error in the Code Analysis settings for the project does.
 
Please modify the source to avoid triggering the rule. I will also post this to the FxCop forums so they can address the problem with rule 1725.

comments

petterh wrote Sep 28, 2009 at 3:26 PM

Impact = Low is wrong: For us it's a showstopper. Turning off the error in the Code Analysis section for the project helps when you do Run Code Analysis from within Visual Studio, but not when you use msbuild.

petterh wrote Sep 28, 2009 at 3:27 PM

It seems to me this is an issue with FxCop rather than with MPFProj...?

wrote Nov 17, 2009 at 8:28 PM

wrote Feb 13, 2013 at 10:30 PM