Hi Arjen, That's exactly what I would want yes. But I had a closer look at the project file format and the way it interacts with the commandline options, and I don't think it will be very easy to implement.
This is an extract of an fxcop project file : <Targets> <Target Name="D:\log4net-1.2.0-beta8\bin\net\1.1\release\log4net.dll" Analyze="True" AnalyzeAllChildren="False"> <Modules AnalyzeAllChildren="False"> <Module Name="log4net.dll" Analyze="True" AnalyzeAllChildren="False"> <Namespaces AnalyzeAllChildren="False"> <Namespace Name="log4net.DateFormatter" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.ObjectRenderer" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.helpers.TypeConverters" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.spi" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.Layout" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.helpers" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.Filter" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.Config" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.Plugin" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.Repository.Hierarchy" Analyze="True" AnalyzeAllChildren="True" /> <Namespace Name="log4net.Repository" Analyze="True" AnalyzeAllChildren="True" /> </Namespaces> </Module> </Modules> <Resources AnalyzeAllChildren="True" /> </Target> </Targets> <RuleFiles> <RuleFile Name="$(FxCopDir)\Rules\DesignRules.dll" Enabled="True" AllRulesEnabled="True" /> <RuleFile Name="$(FxCopDir)\Rules\SecurityRules.dll" Enabled="True" AllRulesEnabled="True" /> <RuleFile Name="$(FxCopDir)\Rules\UsageRules.dll" Enabled="True" AllRulesEnabled="True" /> <RuleFile Name="$(FxCopDir)\Rules\GlobalizationRules.dll" Enabled="True" AllRulesEnabled="True" /> <RuleFile Name="$(FxCopDir)\Rules\ComRules.dll" Enabled="True" AllRulesEnabled="True" /> <RuleFile Name="$(FxCopDir)\Rules\NamingRules.dll" Enabled="True" AllRulesEnabled="True" /> <RuleFile Name="$(FxCopDir)\Rules\PerformanceRules.dll" Enabled="True" AllRulesEnabled="True" /> </RuleFiles> as you can see, you can't just use a fileset for the targets unless you always want all types to be analyzed ... Gert ----- Original Message ----- From: "Arjen Poutsma" <[EMAIL PROTECTED]> To: "Gert Driesen" <[EMAIL PROTECTED]> Cc: <[EMAIL PROTECTED]> Sent: Tuesday, August 12, 2003 3:45 PM Subject: RE: [nant-dev] FxCop Tasks Ok, I think I get it now :-). Basically, you want a fxcop task that can be used as follows: <fxcop report="myreport.fxcop"/> Which only checks the assemblies defined in the project file against the rules defined in the project file. <fxcop report="myreport.fxcop"> <targets basedir="bin"> <includes name="**/*.dll" /> </targets> </fxcop> Which checks the assemblies in the targets fileset against the rules defined in the project file. <fxcop report="myreport.fxcop"> <targets basedir="bin"> <includes name="**/*.dll" /> </targets> <rules basedir="c:\MyRulesDir"> <includes name="**/*.dll" /> </rules> </fxcop> Which checks the assemblies in the targets fileset against the rules defined in the project file, in addition to the ones specified in the project file. So the task should work like this: read the .fxcop project file, changes the <targets> block if a targets fileset was specified, adds custom rules to the <rulefiles> block if specified, writes this to a temporary file somewhere, and runs fxcopcmd over it. Right? Arjen ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers