Gendarme is a extensible rule-based tool to find problems in .NET applications and libraries. Gendarme inspects programs and libraries that contain code in ECMA CIL format (Mono and .NET) and looks for common problems with the code, problems that compiler do not typically check or have not historically checked.
Gendarme uses the Cecil library to introspect code.
- Because we often repeat our mistakes. The biggest one being not to review things we know.
- Because it’s a lot funnier (and safer) to write a rule than to review millions of source lines of code (SLOC) to ensure it’s being followed.
Gendarme was originally created by Sebastien Pouliot to assist in the security auditing process in Mono. Aaron Tomb later integrated his .NET bug-finding code (supported by the 2005 Google Summer of Code, GSoC) into the same framework. Since then the number of contributors and rules has been growing.
Many Gendarme tasks have been realized in Google Summer Of Code (GSoC): three projects in 2007, one in 2008 - and in the Google Highly Open Participation (GHOP): 17 tasks providing 40 rules (2007/2008), renamed Google Code In (2010/2011) : 30 tasks providing 30 rules and a few tools/templates. If you are interested in such tasks please see the StudentProjects page.
Gendarme’s rules are executed against user code by using a ‘runner’. This is the application responsible to load the rules, user assemblies, analysis and finally reporting defects. Gendarme currently ships with two different runners.
A console-based runner is available to use Gendarme, and the rules, on your own compiled assemblies. It is capable to output its results directly on the console, into XML files or into nice looking HTML reports.
This runner is the one that includes the most features. To see every options just type the following command in your terminal:
A System.Windows.Forms-based GUI runner is also part of the Gendarme distribution. This is a step-by-step, wizard-based, runner that allows you to select assemblies, rules, options and report the analysis results just like the console runner does (i.e. text, xml or html reports). However it has fewer options (to remain simple) than the console runner.
Daniel Nauck (dna) also created a NAnt task for Gendarme. Unlike the previous one this is not a runner itself but calls the console runner, which reduce the build dependencies.
Gendarme is modular and load all of it’s rules from assemblies, i.e. there are no hard-coded, static, rules.
For the console runner the list of assemblies to load rules from is defined in the rules.xml configuration file and can be adapted to different needs (e.g. project specific rules). The wizard runner will display all rules from every assemblies present in it’s installation directory.
Current rules are divided into the following categories/assemblies:
- Gendarme.Rules.Design.Linq (new in 2.2)
- Gendarme.Rules.Maintainability (new in 2.0)
- Gendarme.Rules.Security.Cas (new in 2.2)
- Gendarme.Rules.Serialization (new in 2.0)
- Gendarme is part of mono-tools and is available on most recent Linux distributions
- Packages for many distributions and, from time to time, preview versions are also available from the openSUSE Build Service
- Win32 installers (msi) are available on GitHub web site. The .NET framework version 3.5 (or later) needs to be installed prior to running the setup.
Binaries only (multi-platform)
- ZIP files that contains Gendarme’s binaries and configuration files are also available on the GitHub web site. They requires Mono 2.8 or the .NET framework 3.5 to be installed to execute properly.
- From Git (master):
git clone https://github.com/mono/mono-tools.git
- Browse Git for individual files
Other Cool Stuff
- What’s planned ? Gendarme.Roadmap
- What’s happening ? You can read real-time news on Gendarme’s development on its Ohloh’s journal.