Finally, I found out why the are not recognized on one
computer.
My build file looked like this:
[...]
On the computer where it did not work, the TMP environment variable was set
to d:\TMP. When I changed it to d:\t
Hi,
we are using Nant for automated builds of an ASP.NET project. The developers
have VS.NET installed on their computers, whereas the compile servers have
only the .NET SDK and Nant.
Our project references some third-party assemblies which are installed on
the developers' computers. The path to
Have you already tried an analyze on your VSS-DB?
> -Ursprüngliche Nachricht-
> Von: Felice Vittoria [mailto:[EMAIL PROTECTED]
> Gesendet: Samstag, 25. Juni 2005 00:39
> An: Nant-Users (E-mail)
> Betreff: [Nant-users] vsshistory task - something puzzling
>
>
> Hello all,
>
> I have some
> Presumably the bit that is unclear to use is the use of "not"
> in the test...
>
> I.e. instead of using
>
>
> whatever
>
>
> You can use
>
>
> whatever
>
>
> Is that the intended replacement Gert?
BTW: The "not" operator is not documented in v0.85-rc3.
Regards,
M
> I"ve been away for a while and now I"m back into using Nant. I downloaded
the latest
>version [ NAnt 0.85 (Build 0.85.1986.0; nightly; 6/9/2005) ] and noticed a
difference in
>behavior when using the if and ifnot tasks. If I use the ifnot task, I
get the
>following message: "Task is depreca