mscomm32.msm
 
Dave Williamson
Clear Sky Software
[EMAIL PROTECTED]
www.clearskysoftware.com


 


From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Derek Cicerone
Sent: Thursday, August 17, 2006 5:56 PM
To: 'Dave Williamson'; 'Bob Arnson'
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MSComm32.ocx MSM not registering ocx

Which msm is causing problems (what is its exact name)?

 

Thanks,

Derek

 

From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Williamson
Sent: Thursday, August 17, 2006 2:46 PM
To: 'Bob Arnson'
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MSComm32.ocx MSM not registering ocx

 

The versions of the file are the same.  Actually it was the same physical file just to be sure (I used the extracted file from the msm).

 

OK.  So now I'm back to using the Tallow generated code (because it works) but I'm at a cross roads.  Rob has said that the component's GUID is super important when trying to keep up with shared files installed on a machine ... in this case the shared file is a vb 6 ocx control.  And the Tallow code does not match the Dark code of the msm so technically I should not use the msm component GUID with the tallow code because they are different ... yet what is being accomplished is installing a shared file, mscomm32.ocx,  on the end user's system32 dir, registered, and reference counted ... and that does need to be coordinated with other folks installing that same file.

 

If I use the same GUID then the mscomm32.ocx should not be uninstalled prematurely if my app is uninstalled and other apps that have installed the ocx are still installed.

 

If I use a different GUID then the mscomm32.ocx could be uninstalled if the basic reference counting is out of whack.

 

What a [EMAIL PROTECTED] if you do and [EMAIL PROTECTED] if you don't situation.

 

Dave Williamson
Clear Sky Software
[EMAIL PROTECTED]
www.clearskysoftware.com

 

 


From: Bob Arnson [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 17, 2006 4:48 PM
To: Dave Williamson
Cc: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] MSComm32.ocx MSM not registering ocx

Dave Williamson wrote:

The Dark output showed some interesting constructs that were not directly in the tallow code but seemed like they were the same thing but represented in a different manner.

Yes, tallow doesn't know how to use the strongly-typed COM-registration elements. (Heat, in WiX v3, does.) So it just turns them into registry values.

The only other suggestion I can think of is to check the files in the merge module, to make sure you're using the same version. It's been ages since I worried about COM evils.<g>

-- 
sig://boB
http://bobs.org
-------------------------------------------------------------------------
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

Reply via email to