We heavily use a mixture of CC.Net, NAnt and MSBuild to automate our
builds. We have NAnt call MSBuild to compile everything and then use
NAnt to run our tests (nunit) and do most of the packaging/publishing
steps.

 

I am glad to hear that the main NAnt project will continue to be
developed. (As long as you are making it work with .Net 4.0, could you
make it so the solution can compile from Visual Studio?)

 

I too would like to see the NAntContrib project reopened as we use
several tasks from this group. Some of our code is still VB6 and I have
been trying to move the build for this component to NAnt. I ran into a
roadblock as the VB6 task is broken and I get the following error:
([vb6] Type library file 'c:\windows\system32\vbscript.dll\3' does not
exist.)

 

Using <exec> the code compiles fine so I made a copy of the VB6 task and
fixed it. I also added a "force" attribute to always build the output. I
would be happy to share my changed code.

Tony Bjerstedt

Software Engineer

Hollander, a Solera Company

14800 28th Ave N., Suite 190

Plymouth, MN 55447

Audatex Net:         595-3235

Direct:                    (763)519-3235

Email: tony.bjerst...@audatex.com

www.hollandersolutions.com <http://www.hollandersolutions.com/> 

 

From: Markus Ewald [mailto:cy...@nuclex.org] 
Sent: Monday, March 14, 2011 12:08 PM
To: nant-users@lists.sourceforge.net
Subject: Re: [NAnt-users] Are people still using NAnt

 

On 3/14/2011 4:54 PM, Bob Archer wrote: 

Hi Folks... we rely heavily on NAnt for our builds. But, it seems that
development and activity here has really slowed down. Have people moved
to MS Build or is NAnt just at that stage where it is stable enough so
people don't have problems with it and it doesn't need a lot of changes?

 

I'm using NAnt for all of my builds as well. MSBuild is just too icky
for me -- functional programming is a good match for build dependencies,
but MSBuild carries the idea too far (take ItemGroups as an example). In
the end, it just makes you jump through hoops and kills readability. All
imho, of course.

I don't think NAnt itself needs any and I can't remember a single bug
ever surfacing in the time I used it. But adding some new stuff
definitely wouldn't hurt, preferably through NAntContrib, as others
mentioned.

So far, I've taken care of my biggest itches by writing my own task
library
(https://devel.nuclex.org/sideprojects/svn/tasks/Nuclex.NAnt.Tasks/trunk
), containing tasks for 7-Zip, Subversion and for removing nodes from
XML documents. I'd love to contribute any of those to NAntContrib or
whatever NAnt development goes, but it has grown pretty silent again
recently.





BOb

 

 

-Markus-


- ---------------------------------------------------------------------------

 

PRIVILEGE AND CONFIDENTIALITY NOTICE
The information in this electronic mail (and any associated attachments) is 
intended for the named recipient(s) only and may contain privileged and 
confidential information. If you have received this message in error, you are 
hereby notified that any use, disclosure, copying or alteration of this message 
is strictly prohibited.  If you are not the intended recipient(s), please 
contact the sender by reply email and destroy all copies of the original 
message.  Thank you.

 


 --------------------------------------------------------------------------
------------------------------------------------------------------------------
Colocation vs. Managed Hosting
A question and answer guide to determining the best fit
for your organization - today and in the future.
http://p.sf.net/sfu/internap-sfd2d
_______________________________________________
NAnt-users mailing list
NAnt-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nant-users

Reply via email to