[NAntC-Dev] RE: NAnt install

[John Cole]

James,   I was able to compile todays NAnt and NAntContrib and the MSI task worked.  However when I load the install on a virtual machine with a fresh copy of XP, I get the following error during installation:   Module C:\Program Files\NAnt\Tools\VSNetAddin\VSUserControlHost.dll failed to register.  HRESULT -2147024770. Contact your support personnel.   Hitting the retry failes again.  Pressing Ignore allows the install to finish.   Otherwise the install seems to work and run.   It does need to check for .Net, however.  I installed it on a VM without .Net and of course ran into problems ;-)  Aborting until .Net is installed, or hitting the MS site for the download would be very nice.   John -----Original Message----- From: James Geurts [mailto:[EMAIL PROTECTED] Sent: Friday, June 18, 2004 10:52 PM To: [EMAIL PROTECTED]; John Cole Subject: NAnt install 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. ------------------------------------- This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail.