FxCop 1.35 Released!


We are pleased to announce the release of FxCop 1.35. Please visit http://www.gotdotnet.com/team/fxcop to download it.


Changes since FxCop 1.32:




  • FxCop now only runs on .NET Framework 2.0, however, it supports analyzing all versions of .NET Framework.


  • Support for in source suppression via the SuppressMessageAttribute* (.NET 2.0 only).


  • New WiX-based installer


  • Ability to search GAC for missing references


  • New rule – Design\ExceptionsShouldBePublic


  • New rule – Usage\AttributeStringLiteralsShouldParseCorrectly


  • New rule – Security\SecurityTransparentAssembliesShouldNotContainSecurityCriticalCode


  • New rule – Security\SecurityTransparentCodeShouldNotAssert


  • New rule – Security\SecurityTransparentCodeShouldNotReferenceNonPublicSecurityCriticalCode


  • Noise reduction against generated code and C++/CLI

*In source suppression allows the exclusion of FxCop messages to be expressed in source by applying the System.Diagnostics.CodeAnalysis.SuppressMessageAttribute to the relevant source item. Alternatively the attribute can be applied at the assembly level, specifying the target and scope of the suppression.


 


To obtain a well-formed SuppressMessageAttribute in FxCop, simply right-click on the message and choose Copy As -> SuppressMessage or Copy As -> Module-level SuppressMessage.


 


For more information about in-source suppression, see In Source Suppression Overview.

Comments (13)

  1. Sam Gentile says:

    You know what? Owning a pool really sucks-). Oh, it’s great to go in but not a lot of fun spending most…

  2. CoqBlog says:

    Sorti depuis début avril en Release Candidate, la version finale de FxCop 1.35 est maintenant…

  3. One thing you might notice from today, is that when you fire up FxCop 1.35, the rule URLs are now redirecting…

  4. RHarding says:

    Can I update FxCop in Visual Studio 2005 with this version, ( is this version "better" than whats in Vs2005? ).

    If not, can I import the new rules into Vs2005 atleast?

  5. Stu says:

    It’s great that a newer version has come out and is running on 2.0.  However, I don’t have 2.0 installed and was looking for the 1.32 version that will run under 1.1.

    Where can I get that?

  6. davkean says:

    Stu,

    You only need to install the .NET Framework 2.0. FxCop 1.35 supports analyzing both .NET 1.x and 2.0 assemblies. We do not recommend using FxCop 1.32 as it gives incorrect advice for some security rules, plus 1.35 has a heap of bugs fixes.

    Regards

    David

  7. We have had a lot of users contacting us since we released FxCop 1.35, asking for a link to be able to…

  8. Sam Gentile says:

    You know what? Owning a pool really sucks-). Oh, it’s great to go in but not a lot of fun spending

  9. We have had a lot of users contacting us since we released FxCop 1.35 , asking for a link to be able

  10. One thing you might notice from today when you fire up FxCop 1.35 , is that the rule URLs are now redirecting