>From: "Gert Driesen" <[EMAIL PROTECTED]> >Sent: Wednesday, September 29, 2004 12:50 PM
[re: using the config file to autoload the contrib and user extension directories] > While that will ofcourse work, its definitely not the recommended procedure. Why not? It seems to me that if you're using a library of tasks, it makes more sense to treat that as a configuration item, not a build item. Otherwise you clutter up the build script with load tasks, which relate more to NAnt than the thing being built. If you decide to use a common include file to simplify that problem, then may wind up paying the expense of loading a dozen .dlls when all you need for a specific build is just one. Either way, you either have a hardwired path to the contrib directory that may not be valid on all machines, or else you have to go through extra configuration steps (e.g. defining an environment variable) anyway. Finally, it just increases the learning curve for the build engineer who is often a junior engineer, and not necessarily even a programmer. (No offense to the many highly skilled build engineers, but they're the exception, not the rule.) I can see that in some cases using loadtask may be better, but I don't see that it needs to be a hard and fast rule. Gary ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
