RE: [NAnt-users] Environment variable issue.

2006-02-13 Thread Melissa Kacher
Please see the nant docs, docs on tasks, go to the exec task. The documentation that you want you want to read is on the resultproperty attribute.   Here is link directly to the documentation that you need:   http://nant.sourceforge.net/release/latest/help/tasks/exec.html   From: [EMAIL PR

Re: [Nant-users] environment::get-variable usage

2005-06-06 Thread Clayton Harbour
CTED] *Sent:* Monday, June 06, 2005 2:08 PM *To:* Kevin Kirkpatrick; nant-users@lists.sourceforge.net *Subject:* RE: [Nant-users] environment::get-variable usage You need single quotes round the variable name, otherwise NAnt will try to evaluate it as a property: value="${environment::get-v

RE: [Nant-users] environment::get-variable usage

2005-06-06 Thread Kevin Kirkpatrick
Kevin Kirkpatrick; nant-users@lists.sourceforge.net Subject: RE: [Nant-users] environment::get-variable usage   You need single quotes round the variable name, otherwise NAnt will try to evaluate it as a property:       I'm pretty sure that the environment variable lookup is not case sensitive so &#

Re: [Nant-users] environment::get-variable usage

2005-06-06 Thread Merrill Cornish
Kevin, Everything inside the ${ ... } will be evaluated UNLESS it is quoted. Since I assume BLOCK is the name of an environment variable rather than of a property to be evaluated, try single quotes around it. Merrill --- This SF.Net email i

RE: [Nant-users] environment::get-variable usage

2005-06-06 Thread Bill Martin
You need single quotes round the variable name, otherwise NAnt will try to evaluate it as a property:       I'm pretty sure that the environment variable lookup is not case sensitive so 'BUILD' and 'build' should both work.   HTH,   Bill   -Original Message-From: [EMAIL PROTECT

RE: [Nant-users] Environment

2002-11-06 Thread Patrick Näf
ge.net]On Behalf Of Ian MacLean > Sent: Donnerstag, 31. Oktober 2002 19:06 > To: Smith, Eric V. > Cc: [EMAIL PROTECTED] > Subject: Re: [Nant-users] Environment > > > Sounds like a good idea for new task. Unfortunately the .Net framework > has no facilites for setting env vars ( be

Re: [Nant-users] Environment

2002-10-31 Thread Ian MacLean
Sounds like a good idea for new task. Unfortunately the .Net framework has no facilites for setting env vars ( believe it or not ) so this would have to use PInvoke or managed C++. Ian -Original Message- From: [EMAIL PROTECTED] [mailto:nant-users-admin@;lists.sourceforge.net]On Beh

RE: [Nant-users] Environment

2002-10-31 Thread Patrick Näf
> What about embedding the external program call in a batch file > and start the > batch file with the setting of the environment variables? I thought of it myself but would have preferred an attribute to the exec task (or any other method built in to nant) so I wouldn't have to "pollute" the pro

RE: [Nant-users] Environment

2002-10-30 Thread Smith, Eric V.
Look at the sysinfo task: http://nant.sourceforge.net/help/tasks/sysinfotask.html > -Original Message- > From: [EMAIL PROTECTED] > [mailto:nant-users-admin@;lists.sourceforge.net]On Behalf Of > Patrick Näf > Sent: woensdag, oktober 30, 2002 3:26 PM > To: [EMAIL PROTECTED] > Subject: [Nant

RE: [Nant-users] Environment

2002-10-30 Thread Henk van Jaarsveld
What about embedding the external program call in a batch file and start the batch file with the setting of the environment variables? Regards, Henk -Original Message- From: [EMAIL PROTECTED] [mailto:nant-users-admin@;lists.sourceforge.net]On Behalf Of Patrick Näf Sent: woensdag, oktober

Re: [Nant-users] Environment variables

2002-08-22 Thread Ben Lowery
yup, check out the sysinfo task. that should populate the sys.env.* properties, where * corresponds to your enironment variables. --b - Original Message - From: Damon Allison To: [EMAIL PROTECTED] Sent: Tuesday, August 20, 2002 4:22 PM Subject: [Nant-users] Environment variables Hello