This works well, but there is a little more that needs to happen. Right now the basedir maps to the WorkingDirectory of the Process. This is done in the base class of ExecTask, ExternalProgramBase. I've updated the code so that the program is checked to see if it is rooted. If it is, it is left alone. This allows the use of a basedir/WorkingDirectory while being able to specify an absolute program location.
Now that I think about it, we may just want to define a working directory attribute/property for the ExecTask/ExternalProgramBase. In the case of a compiler, the basedir makes sense for a WorkingDirectory. I'm thinking in the general ExecTask it should really be left up to the user. Thoughts? > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nant-developers- > [EMAIL PROTECTED]] On Behalf Of Ian MacLean > Sent: Monday, June 24, 2002 10:30 AM > To: John Lam > Cc: [EMAIL PROTECTED] > Subject: Re: [nant-dev] ExecTask semantics are confusing > > John Lam wrote: > > >Does this sound like a reasonable patch to ExecTask.cs? Anyone want to > >drop it in? > > > > > Committed. > > Ian > > > > ------------------------------------------------------- > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > Nant-developers mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/nant-developers ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Nant-developers mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-developers
