> > <loadtasks path="..\foo\tasks.dll"> > </loadtasks> > or > <loadtasks> > <fileset> > <includes name="..\foo" /> > </fileset> > </loadtasks> > .... > > What do you guys think?
OK. I know get the place of <loadtasks> in the story and it makes complete sense to me. Lose the old <taskdef>. Man, what a dud! :) A single file or a fileset makes sense also. >From your example, I can't tell whether the path= attribute is for a single file (eg: c:\lala\bob\lili\peterTask.dll") or a filespec (eg: "c:\**bob**\*.dll" ) . If it's the former, then the name file= would work better IMO, just like in <copy>. If it's the latter, then I'd suggest sticking to the child <fileset> to alleviate confusion. ------------------------------------------------------- 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
