mailto:[EMAIL PROTECTED]
Sent: 20 October 2005 17:31
To: Crowhurst,Christian; nant-users@lists.sourceforge.net
Subject: RE: [Nant-users] Developers using NAnt Directly
This is a really great addition to this thread, thanks Christian, you've
really brought this into clear focus for me!
This is a really great addition to this thread, thanks Christian, you've
really brought this into clear focus for me!
When you talk about separate targets in this context, do you put targets
into separate build files for each type of build, or do you use
branching and manage all the build types in
Hi Kelly
because I wanted a seamless build process for developers (they should
not be required to learn nant), I've set up a CCNet server which
invokes NAnt. The solution task didn't work out well in my context (I
met to many cases of failure, mainly because of managed c++ projects ),
so I backed
Title: Re: [Nant-users] Developers using NAnt Directly
I didn't mean to imply that (our)
developers shouldn't or don't build locally. In our company in fact they
do and can catch code errors this way before checking code in. Whether or
not they build locally with Nant is
On 10/20/05, Evan Levy <[EMAIL PROTECTED]> wrote:
> This is what we do. Developers develop with Visual Studio, and the
> build automation happens with Nant on the server pulling code from
> source control. In fact, our developers don't really need to build
> locally at all (but they do anyway).
This is what we do. Developers develop with Visual Studio, and the
build automation happens with Nant on the server pulling code from
source control. In fact, our developers don't really need to build
locally at all (but they do anyway). They can launch a server-side Nant
build from a custom web
Well, I think that comes down to a cost/benefit analysis. If the benefits of
building with NAnt outweigh the cost of learning, then
your developers will likely hop on the bandwagon.
I phased it in at my workplace, where we do mostly web apps. Our devs use
VS.NET for coding, testing, and debugg
