Share via

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

  • Article

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

  • Anonymous
    February 29, 2008
    PingBack from http://www.alvinashcraft.com/2008/02/29/daily-bits-february-29-2008/

  • Anonymous
    May 04, 2008
    How to do this from within VisualStudio2005? What is the format of the XML config to do this in the .csproj file?

  • Anonymous
    August 17, 2008
    After what has to be the longest beta period of a product (after Gmail) - we've finally released

  • Anonymous
    September 07, 2008
    After a very long time, an FxCop update has been released . Here is a list of all that has changed: 200

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

  • Anonymous
    January 29, 2009
    Thank you for submitting this cool story - Trackback from DotNetShoutout