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? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nant-developers- > [EMAIL PROTECTED]] On Behalf Of Gerry Shaw > Sent: Tuesday, April 30, 2002 9:45 AM > To: [EMAIL PROTECTED] > Subject: [nant-dev] Fwd: NAnt patch to support MCS-style command line > arguments > > If anything ever came from the talk about using a > machine config file to specify the compiler to use > this contribution might be useful. > > Note: forwarded message attached. > > > __________________________________________________ > Do You Yahoo!? > Yahoo! Health - your guide to health and wellness > http://health.yahoo.com _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
