Jean, > I think tomas was saying there's no gain in losing taskdef, only loss, > like my point.
True. But the <loadtasks> alternative Ian proposes sounds good, as it accomplishes the same as taskdef, but does it in a more nant-like way. I'm happy to change a line or two in my buildfiles for this. My only added comment on loadtasks would be to have it support specifying a single file name, not necessarily a full directory. I imagine something like this would be my choice: <loadtasks path="..\foo\tasks.dll"> </loadtasks> or <loadtasks> <fileset> <includes name="..\foo" /> </fileset> </loadtasks> Basically, the same as Ian proposes, but I'd have loadtasks examine the contents and see if it references a file or a directory: if the former, just load that one and that's it; otherwise scan for task assemblies. This would give us all the functionality of the old TaskDef, while supporting the scanning mechanism used now. What do you guys think? -- Tomas Restrepo [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: ValueWeb: Dedicated Hosting for just $79/mo with 500 GB of bandwidth! No other company gives more support or power for your dedicated server http://click.atdmt.com/AFF/go/sdnxxaff00300020aff/direct/01/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
