Ian astounded with:
> It works with 0.85. There have been a number of
> fixes and your build file works perfectly with it. I had a stab at
> getting it working with 0.84 but unfortunately 0.84 does not:
I downloaded and tried it (Sorry, I should have done that first) and it
works beautifully (cha
; for extensions.
[echo] Setting new value
[setenv] Setting env var X to test
[echo] X = test
build:
This is probably somthing worth considering adding to NAnt. Of course we
would need to use platform #ifdefs as the above is windows specific.
Ian
Eric D
-Original Message
> Subject: RE: [Nant-users] Creating/setting env variables
>
> .NET can, on the other hand, start a process with particular
environment
> variables set. The task has an element for this
> purpose. I use it to call devenv.exe and set the appropriate PATH,
> INCLUDE, and LIB
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Eric Deslauriers
> Sent: woensdag 8 december 2004 21:31
> To: NAnt Users mailing list
> Subject: [Nant-users] Creating/setting env variables
>
> I'm using Covera
[EMAIL PROTECTED] [mailto:nant-users-
> [EMAIL PROTECTED] On Behalf Of Merrill Cornish
> Sent: Wednesday, December 08, 2004 12:44 PM
> To: Eric Deslauriers; NAnt Users mailing list
> Subject: Re: [Nant-users] Creating/setting env variables
>
> Eric,
>
> Someone may have a
Eric,
Someone may have a clever/devious answer, but you may find that you can NOT set
environment variables from within NAnt--because .NET won't let you set
environment variables, just read them. It's a security thing.
Merrill
---
SF email
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
