Hey all,

 

I just checked in my changes to the NAntContribInstall.include file.  I replaced most of the old functionality with 8 new targets (give or take).  There are targets that build merge modules for NAnt and merge modules for NAntContrib.  I basically split each product into binary files, source & test files, and documentation files.  There is a merge module representing each of those categories.  Then there is a main msi target that combines all merge modules for NAnt & NAntContrib. 

 

After installing, I was able to build a package install of NAnt using the deployed NAnt and it’s accompanied directory structure.  I was not able to build NAntContrib, however.  I think that some changes need to be made to NAntContrib’s build scripts in order to have the NAnt and NAntContrib source trees co-exist in the same directory structure.  Either that, or I need to change where I deploy the files...

 

So anyway, if you get a chance, try it out and let me know if there are problems, etc.

 

Jim

 

 

P.s. I came across a thread from a Microsoft blog describing why randomly generated component guids are bad.  So it looks like we’ll stick with the current solution, and I should probably change some of the logic (for generating new components for assemblies & COM objects) so that those guids are consistent, as well.

Reply via email to