Scott Hernandez wrote: >Yeah, I was just thinking about this the other day. > >With the conversation about aliases, and paths and stuff, this seems >like something we need. > >Should we follow the .Net config standard and used the .config file like >ASP.Net? Then we can do the whole config inheritance and allow >machine/user/directory configurations. > >This file might be a good place to do the following: >1.) Specify Task Assemblies that should be loaded >2.) Specify program locations >3.) Provide central configuration for machine/user specific task >settings (program locations, etc.) >4.) Configure aliases and default task settings... > >Thoughts? > My view on this is that it should be a simple as possible. Add configuration where it absolutely necessary. Too much configurablilty starts adding a lot of confucion to new users. For number 1) I like the idea of nant finding assemblies in certain directories rather than having to specify each individual assembly. that way you can just drop in a new task assembly and go without having to edit anything.
Ian _______________________________________________________________ Have big pipes? SourceForge.net is looking for download mirrors. We supply the hardware. You get the recognition. Email Us: [EMAIL PROTECTED] Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
