Thanks... that works great. I changed it to return a zero if error level
was 1 otherwise to return errorlevel.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Brass
Tilde
Sent: Friday, February 08, 2008 10:43 AM
To: nant-users@lists.sourceforge.net
Subject
Chris,
This does not appear to be a NAnt issue. Can you try running a console appp
that use Path.GetTempFileName () ?
Gert
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Chris Weiss
Sent: vrijdag 8 februari 2008 21:54
To: nant-users@lists.sourceforge.ne
I've been editing a NANT file that does delay-signing and then creates
policy files. After running the file, NANT suddenly started throwing
the following errors, regardless of what build file I feed it (even a
simple "hello world" build file fails).
C:>\nant -f:test.build -debug
(numerous loadtask
Bob Archer <[EMAIL PROTECTED]> wrote:
> So, I have a build tool which comes with a batch file to call it. The
> batch file calls the build tool which sets the errorlevel. It actually
> sets it to 1 for success. Is it possible it doesn't get back to
> nant... I would expect nant to see the one and
Ok,
So, I have a build tool which comes with a batch file to call it. The
batch file calls the build tool which sets the errorlevel. It actually
sets it to 1 for success. Is it possible it doesn't get back to nant...
I would expect nant to see the one and think there was a failure but
that does
Yes, it does. 0 = success, non-zero = fail.
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bob
Archer
Sent: Thursday, February 07, 2008 10:37 PM
To: nant-users@lists.sourceforge.net
Subject: [NAnt-users] exec