I'm using CoverageEye for code coverage and have the need to set environment variables that may or may not exist from within my NAnt task.
Since unsetting an env var usually makes it not exist, this is problematic. The key requirement is that the any future env calls or exec calls from NAnt need to pick up the new env variables and values. I found this: http://weblogs.asp.net/jdennany/archive/2004/11/08/254095.aspx However, it also works on the supposition that the env variable already exists. Finally, is there any way to make sys.env.PATH be case INsensitive? Some of our machines use "Path", others use "PATH" and sys.env.PATH won't find "Path". Thanks for any help! Eric D ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Nant-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/nant-users
