FxCop is a free static code analysis tool from Microsoft that checks .NET managed code assemblies for conformance to Microsoft’s .NET Framework Design Guidelines. Unlike StyleCop, or the Lint programming tool, for the C programming language, FxCop analyzes the compiled object code, not the original source code.
It uses CIL parsing, and callgraph analysis to inspect assemblies for more than 200 different possible coding standards violations in the following areas:
– COM (Interoperability) – rules that detect COM Interop issues.
– Design – rules that detect potential design flaws. These coding errors typically do not affect the execution of your code.
– Globalization – rules that detect missing or incorrect usage of information related to globalization and localization.
– Naming – rules that detect incorrect casing, cross language keyword collisions, and other issues related to the names of types, members, parameters, namespaces, and assemblies.
– Performance – rules that detect elements in your assemblies that will degrade performance.
– Security – rules that detect programming elements that leave your assemblies vulnerable to malicious users or code.
– Usage – rules that detect potential flaws in your assemblies that can affect code execution.
– Maintainability – rules that detect maintenance issues.
– Portability – rules that detect portability issues.
– Reliability- rules that detect correct memory and thread usage.
FxCop includes both GUI and command line versions of the tool. Microsoft Visual Studio 2005 and Visual Studio 2008 Team System Development Editions both include a “Code Analysis” feature based on FxCop.
For Visual Studio 2010 the corresponding, and slightly enhanced, static code analysis features are included in the Premium and Ultimate editions. FxCop 10.0 is included in the Microsoft Windows SDK for Windows 7.
FxCop – Wikipedia.
I’ve recently purged everything Visual-Studio .NET related in favour of SharpDevelop, [which is a wonderful C++/C# editor], while configuring things up there I’ve noticed that FxCopy (which is a part of WinSDK installation) wasn’t configured,
While I did downloaded the SDK before But I’ve figured that it will be much *cooler* to have *just this part* portable as $hit, since I’m already using the portable version of SharpDevelop.
While FxCop Installer [codeplex] ripped successfully the installer..
it was still wrapped with the ugly Windows-Installer hell..
After I’ve extracted the HELL of it (let us not discuses my method here&&now..) I’ve got a nice clean MSI archive
[Download #1 – A Clean MSI installer]
The installer above will write the file to their default-location under program-files, and will create shortcuts and such..
so if you are inexperience downloading and extracting the zip, and double-clicking the
install.msi will probably be the easier method for you.
If you are a recklessly s.o.b keep reading..
EDIT: actually from my checking [*spoiler*] neither FxCop nor SharpDevelop (in its portable version) writes any registry values, so it is perfectly safe to continue stripping the installers, and placing the files in any place you’ll like to..
..anyway extracting MSI-archive-installer is relatively easy,
as long you consider the relations between MSI-files, but let us skip this part..
here is what you’ve came-for..
[Download #2 – FxCop 10, No install]
I’ve figured out that both SharpDevelop (in its portable version) and FxCop actually does not write any registry-values, so just grab the *later* zip file, extract it *anywhere* and simply target
fxcop.exe in any program that requires it.
..or just double-click it, it works just fine :]