Ok, I think I get it now :-). Basically, you want a fxcop task that can
be used as follows:
Which only checks the assemblies defined in the project file against the
rules defined in the project file.
Which checks the assemblies in the targets fileset agai
t file,
like so:
But I don't think we can combine this with any of the attributes
described above.
Do these changes make it more useful?
Best,
Arjen
> -Original Message-
> From: Gert Driesen [mailto:[EMAIL PROTECTED]
> Sent: Monday, August 11, 2003 9:42 PM
> To: Ar
use a rules assembly, but turn off a couple specific rules from that
assembly. These are also stored in the project file.
-Original Message-
From: Arjen Poutsma [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 12, 2003 3:37 AM
To: Gert Driesen; [EMAIL PROTECTED]
Subject: RE: [nant-dev] F
ith any of the attributes
> described above.
I agree.
>
> Do these changes make it more useful?
I don't think so ... Really I urge you to use your task on some
"production" assemblies and I'm pretty sure you won't find one that
doesn't violate any
uot;/"create" action.
Ofcourse these are all just personal suggestions/remarks, and by no means I
want to sound ungrateful for the work you've done.
Keep up the good work !
Gert
- Original Message -
From: "Arjen Poutsma" <[EMAIL PROTECTED]>
To: <[EM
Hi,
I've created two new tasks. Before I post them to the list, I would like
to know it there's interest.
First, a wrapper Nant task for FxCop, which can be found at
http://www.gotdotnet.com/team/fxcop. This tools checks for compliance
with the .NET Design guidelines. The task basically wraps FxC
