On 4/19/05, Rainey, Mark (Cleveland) <[EMAIL PROTECTED]> wrote:
So I am guessing the PATH environment variable isn't being set. I runsysinfo and then check the variable with environment::get-variable('PATH').That returns the path but when I echo the ${sys.env.PATH} variable it says
nothing is set.
Hi all, I'm curious
if anyone else has run into memory errors with Nant. (I've been running it on a
box with 4Gig of physical memory and monitoring indicates that our build
system only uses about 2.5Gig of that)
I'm just about to send an email
to the devs list but thought I'd check here as
Hello everyone:
I have been trying to get a labeled version from VSS and it looks like vssget
task is able to do it, but there is not any example, or at least I haven't
found any sample or explanation about it. Could anyone, please, send me a
sample or explain how to create my Nant task to get
This was a recommendation from CCNet users:
There was some recent discussion around this on another thread (the title is
"CCnet 0.9 doesn't appear to see/use PATH variable"). the gist of it is
that it seems like the user's environment variables are not accessible when
running through ccservice.
On 4/18/05, Rainey, Mark (Cleveland) <[EMAIL PROTECTED]> wrote:
> So I am guessing the PATH environment variable isn't being set. I run
> sysinfo and then check the variable with environment::get-variable('PATH').
> That returns the path but when I echo the ${sys.env.PATH} variable it says
> nothi
I am trying to check out some files using the vsscheckout task. When using
it from a service (Cruisecontrol's ccservice) I am running into the
following error about a module not being found:
*
at NAnt.Core.Project.Run() in
d:\Source\nant-20050404T183547Z\src
Hello,
I actually have the same problem, but I don't understand your
explanation. Do you compile the files with VS.Net?
Thank you
Julien
Wilson, Glenn wrote:
Hi,
Problem solved - it had nothing to do with Nant. I had changed my build
file configuration mode to "release" and had forgotten to c
Sorted it. You have to also copy the interop file
Interop.MSHelpCompiler.dll
Thanks to those that replied.
Cheers,
Bill
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Bill Martin
Sent: 15 April 2005 16:39
To: nant-users@lists.sourceforge.ne
