What I have done in the past is have an xml config file for the application that's not related to app.config. This would contain all of the machine specific settings we've been talking about. This would default to some file in the same directory as the executable, say nant.config.xml or some such name. Then have a command line param to nant to specify an alternate config file. This would let you test against 2 different cl.exe's, for example.
I like the idea of having task attributes that are automatically set via attributes, as well as non-task specific attributes. I'd be willing to work on this if the consensus is that it makes sense. Eric. > -----Original Message----- > From: Kevin Dente [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 12, 2002 8:35 PM > To: Smith, Eric V.; [EMAIL PROTECTED] > Subject: RE: [nant-dev] RE: FileSet question > > > Eric, I think that's an awesome idea. > > > I was worried about that same issue of compiler paths > for cl - it would be great if it didn't need to be in > the path, and would be even better if we could support > multiple compiler versions. But would the config file > solution force us to set one compiler version for the > entire build? In other words, if I wanted to have some > projects build with an older compiler and some with a > newer one (something that we've done at work in the > past), could that be supported? > _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
