nunit-dev team mailing list archive

["Charlie Poole" <charlie@xxxxxxxxx>]

Hi Ludovic,
 
You have to use the email that you used when signing up with launchpad.
Maybe you can give them alternative emails as well - I'm not sure.
 
Yes, we should discuss this on the list. I'm copying it so we can get
started.
 
I thought that the built-in style-cop was replacing fxCop. Is it still 
active? I would prefer to use open source tools where we can.
 
I also have tried out Gendarme and it was pretty good. It works on
both Windows and Linux, which is a big point. Also, at my request,
the developer added the ability to specify the framework for which 
you are building so that you didn't get advice like "Use a generic here" 
when building for .NET 1.1.
 
However, I haven't looked at the status of the tools lately so it would
be good if someone did a comparison.
 
Charlie


  _____  

From: Ludovic Delabre [mailto:ldelabre54@xxxxxxx] 
Sent: Saturday, August 01, 2009 1:23 AM
To: Charlie Poole
Subject: [Fwd: Using *Cop tools]


Hi Charlie,
I've send the message bellow to the mailing list some days ago using another
e-mail of mine, so I'm not sure anyone received it...?!

Have a nice day,
Ludovic.

-------- Message original -------- 
Sujet : 	Using *Cop tools	
Date : 	Wed, 29 Jul 2009 07:30:37 +0200	
De : 	Ludovic Delabre  <mailto:ludovic.delabre@xxxxxxx>
<ludovic.delabre@xxxxxxx>	
Pour : 	NUnit Developer Mailing List  <mailto:nunit-dev@xxxxxxxxxxxxxxxxxxx>
<nunit-dev@xxxxxxxxxxxxxxxxxxx>	


Hi everyone,

I was wondering if you plan to use tools like FxCop (or Mono's 

Gendarme?) and/or StyleCop for the future nunit 3.0 ?



For those who don't know about those tools :

* FxCop allows you to analyze assemblies (IL) and reports 

design/performance/security violations. 

http://msdn.microsoft.com/en-us/library/bb429476(VS.80).aspx



I know there's an equivalent project at Mono named Gendarme : 

http://mono-project.com/Gendarme.

Haven't tried it yet, but I will ;-)



* StyleCop works on the source (C# only) to enforce a set of style and 

consistency rules.

http://code.msdn.microsoft.com/sourceanalysis



Both are configurable (which rules you want to enforce/ignore), 

extensible (by writing custom rules) and you always can exclude a 

violation (with justification) using 

System.Diagnostics.CodeAnalysis.SuppressMessage attribute.



At first glance, it's a pain but after using both for a while, I kinda 

like it... ;-)



Have a nice day,

Ludovic.