Share via

FAQ: Why is FxCop 1.32 not available for download? [David Kean]

  • Article

Update:  While SharePoint Portal Server 2003 will not run side-by-side with .NET 2.0, SharePoint Portal Server 2003 SP2 will. For more information, see: https://support.microsoft.com/kb/907763.

We have had a lot of users contacting us since we released FxCop 1.35, asking for a link to be able to download a copy of FxCop 1.32. There appears to be some misconceptions with FxCop 1.35 that we thought we would try to clear up in this post.

Misconception #1: FxCop only analyzes .NET 2.0 assemblies.
Although FxCop 1.35 does require the .NET Framework 2.0 to be installed, it can analyze assemblies compiled against all versions of .NET, including .NET 1.0 and .NET 1.1.

Misconception #2: .NET 1.x and .NET 2.0 cannot be installed on the same system.
Both .NET 1.x and .NET 2.0 and Visual Studio 2002/2003 and Visual Studio 2005 can be happily run side-by-side on a system without affecting each other. If you do find any bugs with these configurations, then we need to know about it.

Misconception #3: FxCop 1.35 requires Visual Studio 2005.
FxCop 1.35 does not and never has, required any version of Visual Studio to be installed.

There are also a number of other reasons why we have not made FxCop 1.32 available:

  • Bugs. 1.32 is over a year old; since then, there have been 150+ bug fixes, (including all in Visual Studio 2005 Code Analysis), that all made it into 1.35.
  • Security. As part of the bugs fixes, we fixed some of the security rules that were giving completely wrong analysis. Because of this, you do not want to base any security decisions based on the analysis that 1.32 gives.
  • Noise Reduction. For 1.35, we have made significant changes to the amount of noise that FxCop fires against code, including generated and C++/CLI.
  • Support. FxCop is, officially, an unsupported tool, however, individual members of the Code Analysis team spend a significant amount of work (and personal) time in the FxCop forums answering questions. Attempting to support old versions of FxCop means that we spend less time working on newer features and better analysis for our customers.

If the above doesn't convince you to move FxCop 1.35, there are also a number of new features such as 5 new rules, in source suppression and GAC support.

Comments

  • Anonymous
    July 12, 2006
    Alors que la version finale de FxCop 1.35 est sortie, David Kean publie sur le blog dédié au logiciel...
  • Anonymous
    July 19, 2006
    Your number of reasons why you have not made FxCop 1.32 available are good but(this is a big BUT) I do not have .Net version 2.0 :) so I need FxCop version 1.32 thanks
  • Anonymous
    July 19, 2006
    Uraz,

    I have provided a link to the install of .NET Framework 2.0 above. It's free to download and it works side-by-side with .NET 1.0/1.1.

    Regards

    David
  • Anonymous
    July 21, 2006
    If you are using Sharepoint 2003 and Visual Studio, you will not want to install the 2.0 framework. Luckily, we found an older copy.
  • Anonymous
    July 21, 2006
    If you are using Sharepoint 2004 and Visual Studio, you will not want to install the 2.0 framework. Luckily, we found an older copy.
  • Anonymous
    August 03, 2006
    the older copy (1.32) could be found fairly easily.
  • Anonymous
    August 10, 2006
    Maybe I'm just looking in the wrong places, but I have a hard time finding v1.32.

    I need it because my company hasn't installed the .NET 2.0 framework on our machines, and won't allow me to install it myself.
  • Anonymous
    August 13, 2006
    Hi, In our company we have only VS.Net2003. To write custom rules using fxCop 1.35 i get error when i try to load the fxcop dlls in the vs.net 2003. And to use .net 2.0 dlls we need to have vs.net 2005. Now any work around to write custom rules..??
  • Anonymous
    August 17, 2006
    There are obviously environments that run with an agreed SOE and therefore not everyone is able to install a new runtime environment at will.

    Why wouldn't you make previous versions available and therefore increase the adoption of FXCOP? What do you have to gain by imposing this constraint?

    Please post a link to the previous version/s
  • Anonymous
    July 10, 2007
    Find answers to commonly asked questions about Visual Studio Code Analysis. General FAQ: Why is FxCop