on 10/22/2004 7:30 PM Merrill Cornish wrote:
This is the reason. Thanks for the help. On the build machine (where this was failing), there is both a PATH and ;PATH environment variable listed. This isn't the case on my machine, so I was not seeing any error messages, and wasn't reading the error message properly.John,
I don't know if this is a typo, but 'sys.env.;PATH' has an illegal character in it: the semi-colon. Also, from the DOS prompt, issue a "set" to see _exactly_ what capitalization of "PATH" is on your machine. For example, on my Windows XP Pro, it's "Path" and sys.env will work _only_ with sys.env.Path.
Merrill
Considering that this environment variable is apparently legal in Windows, should it be legal in NAnt as well? I'm defining "legal" here to mean only that I can define it in the system properties.
John
------------------------------------------------------- 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
