Re: [NAnt-users] solution task: targets v.s. configuration

2006-09-06 Thread Nicholas Duane
I decided to add the "configuration" targets so that I would have the flexibility to do it either way. And these new targets are generic in a sense so I was able to add them to a separate build script. The only requirement is that each build script which includes this common script must defin

[NAnt-users] NAnt book...

2006-09-06 Thread Bob Archer
Not sure if all knew of this book, Expert .NET Delivery Using NAnt and CruiseControl.NET (Expert's Voice in .Net).   But, I highly recommend it for new and experienced users alike. I consider myself a fairly advanced NAnt user and still was able to take many ideas away from this book and

Re: [NAnt-users] solution task: targets v.s. configuration

2006-09-06 Thread Arnette, Bill
I requested the feature because the task is the logical place to do a clean operation since the solution already knows all the intermediate and output files that are generated during a build. Otherwise you have hand-code a 'clean' target in nant using tasks that get all the intermediate and outpu

Re: [NAnt-users] solution task: targets v.s. configuration

2006-09-06 Thread Bob Archer
You can do it either way you want. Basically, in our build we have the basic targets: Clean Version Label Get Compile UpdateDb Deploy The compile task can do either release or debug based on the parameter. However, there was no reason why you can't have two Compile targets etc as you listed bel

Re: [NAnt-users] solution task: targets v.s. configuration

2006-09-06 Thread Karl Palsson
I personally much prefer to have a property in the build file saying whether I'm in debug or release mode. Then I have just three targets in my nant build file, and it's easier to read. Then, in cc.net or wherever, I just call it once in debug mode and once in release mode, I find that a lot mo

Re: [NAnt-users] cvs-update fails with no args; -P option not supported

2006-09-06 Thread Karl Palsson
According to the rc4 documentation, unless you specify a path, it will try and find cvs in your path. So it looks like your cvs binary doesn't support the -P flag, (perhaps it does it by default, which is how I think it definitely should be) If you want to use the built in cvs implementation, yo

[NAnt-users] solution task: targets v.s. configuration

2006-09-06 Thread Nicholas Duane
I know there has already been a discussion on adding another attribute, operation, so we can specify clean, build, rebuild. From the little bit I've read so far (just started using nant) it appears that people are equating targets to clean, build, and rebuild and using a property to determine

[NAnt-users] cvs-update fails with no args; -P option not supported

2006-09-06 Thread Nicholas Duane
Not sure if I already sent this as I accidently hit tab and return. At any rate I just added an update target to my build script. The target is shown below: When I execute the target I get the following error: C:\data\build\pom\Eom\src\Eom>nant update NAnt 0.85 (Build 0.85.2344.0; rc4

[NAnt-users] FW: RE: solution task: debug, release / build, rebuild, clean

2006-09-06 Thread Nicholas Duane
Submitting again after joining nant users. Nick From: "Nicholas Duane" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED], nant-users@lists.sourceforge.net Subject: RE: solution task: debug,release / build,rebuild,clean Date: Tue, 05 Sep 2006 21:08:49 -0400 It just dawned on me that this won't work bec