Yep, NAnt does have support for this. Any assembly named *Tasks.dll is loaded, and any class (not abstract) derived from Task is added to the available tasks list. There is also a temporary TaskDef task that takes an assembly filename as an attribute which does this same thing.
There is another (satellite) project called NAntContrib that has many additional tasks which are not part of the core. Please see nantcontrib.sf.net and the web cvs list of tasks (http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/nantcontrib/NAntContrib/ src/Tasks/). > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nant-developers- > [EMAIL PROTECTED]] On Behalf Of Richard Caetano > Sent: Monday, July 22, 2002 11:23 PM > To: Scott Hernandez; 'Nant-Developers (E-mail)' > Subject: Re: [nant-dev] IFTask PropertyMissing parameter? > > I hope this is not to far off...but it's just a thought. > > When I first looked at the .build layout and noticed the various tasks I > first thought what a perfect place for componentization. What if we > dynamically load available tasks at runtime. We could use reflection to > check existing assemblies (dll's in the same folder) that contain > components > that derive from Task. That way folks can extend NAnt without having to > worry about being kosher with the core. > > Again I hope I didn't dilute the thread with "another voice". =) > > - Richard ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
