s
various timers and potentially multi-tasking.
Hope this helps.
Ken Parrish
Gomez, Inc.
From: Chris Howell [mailto:chris.how...@padresoft.com]
Sent: Thursday, February 04, 2010 5:10 PM
To: Stephan King
Cc: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] Nant VS CC.NEt
Ok perhaps I s
et.
Just my 2 cents, I hope that it's helpful.
Take care,
Mike
From: Phil Sayers [mailto:p...@cds-am.net]
Sent: Thursday, February 04, 2010 5:19 PM
To: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] Nant VS CC.NEt
Think of ccnet as the trigger that fires your nant scripts.
Ccne
...@cds-am.net]
Sent: Thursday, February 04, 2010 5:19 PM
To: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] Nant VS CC.NEt
Think of ccnet as the trigger that fires your nant scripts.
Ccnet will continuously watch "something". That something could be the current
time, one or m
is.how...@padresoft.com]
Sent: Thursday, February 04, 2010 5:10 PM
To: Stephan King
Cc: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] Nant VS CC.NEt
Ok perhaps I should have phrased my question a little better, I am looking
for CI and daily builds. I've used CC.Net before exclusively
integration system for us here.
Stephan
From: Chris Howell [mailto:chris.how...@padresoft.com]
Sent: Thursday, February 04, 2010 5:10 PM
To: Stephan King
Cc: nant-users@lists.sourceforge.net
Subject: RE: [NAnt-users] Nant VS CC.NEt
Ok perhaps I should have phrased my question a little better, I
ry 04, 2010 4:56 PM
To: Chris Howell
Subject: RE: [NAnt-users] Nant VS CC.NEt
You don't choose one over the other, they go hand in hand. CC.NET will handle
all of your source control operations, scheduling, emailing, publishing, etc,
and CC.NET will call into your NANT scripts to do thing
Hi All,
I am looking to introduce a Continuous Integration/build environment to my dev
team which currently has none. What would be the primary advantage(s) to
choosing a NANT too over CC.NET ?
Chris
--
The Planet: dedi
