Hello,
I am building a large solution using the solution task. We
recently moved to from RC3 to RC4 and when the aximp command is called by RC4
the /rcw option is missing. This causes a runtime error. When using the
solution task in RC3 this works correctly. I cannot release any of the
I was wondering if anyone has done any comparisons between BuildForge
and NAnt. What features are better for each product?
Thanks,
David
---
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple
Hello,
I am looking at converting my build files from .84 to .85
when the new version releases. I was experimenting with a recent version of the
nightly code and noticed that properties can no longer have descriptions.
This worked on .84 and I was wondering if this can be added
bac
Merrill Cornish [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 19, 2004 9:45 AM
To: Shaber, David; [EMAIL PROTECTED]
Subject: Re: [Nant-users] Copy misses 'CVS' Directories
David,
On my Windows XP machine, my CVS directories are marked as Hidden. I
don't see an option on the task th
I during one of my builds, after pulling CVS, I attempted to
copy everything to a different location. I noticed that any subfolders named ‘cvs’
was not being copied.
I tried this with the latest nightly build and a test set of
directories and it appears that any subdirectory named ‘cvs
Hello,
I would am running a large build with the –quiet option
from the command line. On Failure, I am using the nant.onfailure property to
call a target and would like to run an external program and see the output on the
screen.
Is there a way to change the log level from Warning to
Misha,
To access a property that has been set in your build file using c#,
try
And in c#
string property = project.Properties[ "my.property" ];
This will set property to the value of my.property.
Also look at the example included with nant called script-sample.build:
When using the call task all targets and dependencies are executed. For
example, if I run execute target 3, I get the output below - notice that
target 2 is executed twice. The first time is by the call task, the
second time is as a dependency of target 1. I tried to get around this
with the force
