Better yet. If you are targeting Windows XP and up and your COM component(s) is not shared among different applications, don't register anything and make your application an "isolated application". See http://msdn.microsoft.com/library/en-us/sbscs/setup/isolated_applications_an d_side_by_side_assemblies_start_page.asp?frame=true
> -----Original Message----- > From: Bill Arnette [mailto:[EMAIL PROTECTED] > Sent: Friday, June 30, 2006 9:59 AM > To: 'wix-users@lists.sourceforge.net' > Subject: RE: [WiX-users] Installing COM components > > Tallow is intended to be used one time to aid in the initial > creation of MSI components for the COM components you need to > install. It is not intended to be used in an automated build. > > The idea is to run Tallow to harvest the components, > including registry entries, and then hand-edit them to add a > component GUID, and set the SourceFile and other paths > appropriately. You would want to change the COM registry > entries to use a directory property such as [TARGETDIR] > instead of the hard-coded paths that Tallow generated. > > Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
