Hmm - thats got me thinking. Currently we auto load 3 types of nant objects - Tasks, types and now functions. However there is only the one corresponding task - <loadtasks>
I'm wondering if we should either :
add two extra tasks <loadtypes> and <loadfunctions>


or have<loadtasks> scan for all nant objects - it might need renaming in that case. Maybe <loadcustom> or somthing like that. I think I'd prefer to scan for all in the one task.

in actual fact if you pass a directory to <loadtasks> now it calls TypeFactory.scandir which will scan for all 3. However passing it an assembly path means it only calls TypeFactory.AddTasks.

Ian

Exactly. That's what Ian has implemented. Perhaps you'll be able to load
functions on demand with something like <loadfunctions> task. I'm also
thinking about supporting functions written in a <script>.

See attached code for actual code used to implement path::* functions.

Jarek






------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers

Reply via email to