It was a couple things actually. 1.) I discovered that I wasn't using the CLSIDs of the DLL for the component in the assembly, and 2) I changed the path to the dll from an actual path to [#component-id] to match the actual component/file id.
Now I'm working on how to fill in all the values that would show up when you look at the compononent's property sheet in Component Services. I think I have it figured out though. :) Jim -----Original Message----- From: Neil Sleightholm [mailto:n...@x2systems.com] Sent: Monday, June 29, 2009 4:21 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Installing VB6 COM+ components I see you got it working, out of interest what was the answer to this? Neil -----Original Message----- From: MacDiarmid, James D [mailto:james.macdiar...@eds.com] Sent: 29 June 2009 18:26 To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Installing VB6 COM+ components Neil, or anyone, I think I have it working for a few of my DLLs, however I have one more question. What if the DLL has more than one CLSID? Do I need to list both of them or just the first one? Thanks, Jim ------------------------------------------------------------------------ ------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
