FAQ: How do I prevent FxCop 1.36 from firing warnings against generated code?


I’ve upgraded from FxCop 1.35 to 1.36 and now FxCop has started to fire warnings against typed DataSets and other generated code. How do I turn this off?

The reason this is occurring is because we changed the way that FxCop analyzed generated code. Whereas previously in 1.35, FxCop would only ignore particular generated code (such as DataSets), FxCop 1.36 will now either ignore no generated code, or all generated code. The former is the default.

To change this behavior and have FxCop skip over generated code:

Using an FxCop project:

  1. Open your FxCop project in FxCop
  2. Choose Project -> Options -> Spelling & Analysis
  3. Check Suppress analysis results against generated code
  4. Click OK

Via the command-line:

  1. Pass the /ignoregeneratedcode switch, for example:

    FxCopCmd.exe /file:MyAssembly.dll /out:AnalysisResults.xml /ignoregeneratedcode

For more information on FxCop’s behavior over generated code, see Correct usage of the CompilerGeneratedAttribute and the GeneratedCodeAttribute.

Comments (6)

  1. KjellSJ says:

    How to do this from within VisualStudio2005? What is the format of the XML config to do this in the .csproj file?

  2. Dave's Box says:

    After what has to be the longest beta period of a product (after Gmail) – we've finally released

  3. After a very long time, an FxCop update has been released . Here is a list of all that has changed: 200

  4. 【原文地址】 FxCop 1.36 Released 【原文发表日期】 20 August 08 08:49 David Kean宣布了 FxCop 1.36的发布 从David的博客中我们能看到以下几处优点

  5. Thank you for submitting this cool story – Trackback from DotNetShoutout