Re: [WiX-users] Installing COM components

2006-07-10 Thread jdrake
Not really. Tallow pulls a bunch of VB6 properties, and additional registry info, which creates additional issues, like possibly blowing up VB with an uninstall. In this case the MSI created by VS.NET only conatins those keys necessary to install the single object. -- View this message in

Re: [WiX-users] Registry Issue

2006-07-06 Thread jdrake
actually need an MSI, so I do not have time to go digging throught the COM+ version and experimenting. Thanks, Joshua -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of jdrake Sent: Wednesday, July 05, 2006 12:21 PM To: wix-users@lists.sourceforge.net

[WiX-users] Registry Issue

2006-07-03 Thread jdrake
I just want to install some COM+ Packages, but I cannot find ANY examples that WORK. So I try it myself and just when I think it all works I discover that: Registry Id=REM_Interface Root=HKCR Key=Interface\{3311A504-2A50-42D8-8E06-A2F6B9D0B614} Action=removeKeyOnUninstall / does NOT remove the

Re: [WiX-users] FW: COM+ custom actions

2006-06-23 Thread jdrake
Now light is complaining about File of Type 'Binary' with name 'pcaexec.dll' could not be found. and the same for pcasched.dll. Both of these are in the Bin and root directory for the Windows Installer XML. Any ideas? Thanks again, Joshua -- View this message in context:

Re: [WiX-users] FW: COM+ custom actions

2006-06-23 Thread jdrake
So not only is Votive-2.0.4103.0.msi missing the pcaext.dll; the command line to candle is case sensitive, which strikes me as odd, since Windows is not. Any word on when the extension will be integrated with Votive? Thanks, Joshua -- View this message in context: