Chris,
Can you send me a small repro for this issue ?
If not, then please send me a debug log of running your build file (NAnt.exe
-debug -logfile:log.txt -buildfile:).
Thanks !
Gert
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> Chris Walto
Thanks Gert, That did the
trick.
From: Gert Driesen
[mailto:[EMAIL PROTECTED] Sent: Tuesday, March 08, 2005 1:39
PMTo: Whitner, Tom;
nant-users@lists.sourceforge.netSubject: RE: [Nant-users]
haltonerror does not appear to work
Hi Tom,
I'm not that familiar with
We just upgraded to .85-rc2 version and started getting an error when
running the solution task. We are getting the error...
[solution] Building 'Project.Name' [debug] ...
[attrib] Setting file attributes for 7 files to Normal.
...
[solution] Project is up-to-date
Hi Tom,
I'm not that familiar with the task, but I
think both the haltonfailure attribute should be set to false on both the
task as the element.
The default value of that attribute is "false" on the
task, but "true" on the element.
I find it rather confusing, but well
...
Gert
Hi All,
I ran into this failure a few times
when Nant was trying to compile a web project.
After removing this temp folder manually,
re-ran the Nant, everything was okay.
This empty temp folder was under my
documents and settings\[current user]\local settings\temp. I guess it was
created by Nant
The environmental variable INCLUDE, LIB and PATH, must be correctly set.
Depending on which version of NAnt you are using, you can also try using
the setenv element. Make sure the cl.exe path is also included.
:
:
I am new to NAnt and trying to build a pre-existing VS.net 2003
solution file. Digging through the archives there seems to be limited
support for c++.net which is where I am having some problems.
If I create a new directory and pull the source code manually, then try to
build with NAnt I get:
Hello,
I have the following scenario, which I’m sure is not
uncommon. I’m building a set of related libraries and applications that
all build in much the same way. To avoid duplicating the XML for the build
target in each project’s .build file, I have defined it in a top-level
.build fi
