I found a reference to version 6.1.98.16 of this file here (including download information): http://support.microsoft.com/kb/957924/
The download path itself for the above here: http://www.microsoft.com/downloads/details.aspx?FamilyId=CB824E35-0403-45C4- 9E41-459F0EB89E36&displaylang=en&displaylang=en I haven't tried it yet to see what that exe exactly contains (the raw .ocx or the .msm). I also don't know if you have to install VS6 first in order to run it or not. Installsite.org lists the msm with the version Neil and you both mention. The merge modules may be available separately here: http://www.microsoft.com/downloads/details.aspx?familyid=f9d19334-61ec-48cf- bb4e-3aec65edd50b&displaylang=en but that control may be buggy from that SP according to installsite.org. Apparently it is listed as part of Visual Basic 6.0 (but the MSM isn't mentioned): http://msdn.microsoft.com/en-us/vbrun/ms788708.aspx Other pages on MSFT sites indicate it was distributed with Visual FoxPro as well. -----Original Message----- From: Daniel Hughes [mailto:daniel.hug...@tait.co.nz] Sent: Wednesday, January 13, 2010 1:35 PM To: General discussion for Windows Installer XML toolset. Subject: Re: [WiX-users] Windows System Folder Thats the version we are installing. Can you please point to how to get this merge module, and for future references and for the other assemblies I need, where do you get official merge modules for Microsoft components? Daniel Neil Sleightholm wrote: > What versions are the two files? This is a standard VB6 custom control, > I must admit I have never heard of an update to this to support more > comm ports, is it an official Microsoft release? > > The "correct" way to install MSCOMM32.OCX is via the Microsoft supplied > merge module, mscomm32.msm, this installs v6.0.81.69 - which version are > you installing? > > Neil > > -----Original Message----- > From: Daniel Hughes [mailto:daniel.hug...@tait.co.nz] > Sent: 12 January 2010 22:53 > To: General discussion for Windows Installer XML toolset. > Subject: Re: [WiX-users] Windows System Folder > > one of the files is MSCOMM32.OCX, this is for handling com ports. We > have a customer who uses a different version of this that provides the > ability to access more com ports. There version is new both in time > stamp and in version. However our installer replaces it, pissing said > customer off. > > Why? It is my understanding that Windows Installer only knows the two > > files are the same if the component GUID matches, ie having the same > name is not enough. The customer in question did not install the file he > > copied it into the required location. Even if he did install it with as > part of some other installer it would have been installed with a > different GUID and so windows installer would not know it was the same > thing and that it should apply its version rules. > > Is my understanding wrong? and if so please explain why our installer is > > replacing our customers (newer) assembly. > > Rob Mensching wrote: > >> Can you provide more information about these files that are getting >> replaced? The Windows Installer its rules for File Version checks >> (documented in the MSI SDK) and they are consistent. You'd have to use >> > a > >> custom action to install files (a huge no-no) to install files >> > differently. > >> The whole design sounds very suspicious right now but more details may >> better explain what is going on and provide suggestions. >> >> On Mon, Jan 11, 2010 at 5:06 PM, Daniel Hughes >> > <daniel.hug...@tait.co.nz>wrote: > >> >> >>> We are moving one of products from a old Install shield installer to >>> > a > >>> WiX installer. >>> >>> The old Installer installs a bunch of assemblies to the System32 >>> > folder. > >>> These assemblies are not produced by us but a required dependencies >>> > of > >>> our software. Install Shield has a replace if older type option so it >>> checks the assemblies version and only installs if the existing >>> > assembly > >>> is older then the one being installed. >>> >>> When we moved to WiX there was no such option. Each assembly gets a >>> component GUID and install shield just goes along and replaces any >>> existing assemblies even if they are newer. This is causing problems >>> > as > >>> some of our customers are running software which relies on >>> > functionary > >>> only available in newer versions. >>> >>> I have heard that a way to get the correct component GUID so windows >>> installer doesn't do bad things is to find official Merge Modules. >>> > These > >>> have proved to be hard to find and if the assembles have been copied >>> > or > >>> installed to Windows32 by some other method it will not work. >>> >>> How do I make sure I don't replace new versions of assemblies which >>> > we > >>> don't produce and don't control. >>> >>> Cheers, >>> Daniel >>> >>> >>> > ======================================================================= > >>> This email, including any attachments, is only for the intended >>> addressee. It is subject to copyright, is confidential and may be >>> the subject of legal or other privilege, none of which is waived or >>> lost by reason of this transmission. >>> If the receiver is not the intended addressee, please accept our >>> apologies, notify us by return, delete all copies and perform no >>> other act on the email. >>> Unfortunately, we cannot warrant that the email has not been >>> altered or corrupted during transmission. >>> >>> > ======================================================================= > >>> >>> >>> > ------------------------------------------------------------------------ > ------ > >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast >>> > and > >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________ >>> WiX-users mailing list >>> WiX-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/wix-users >>> >>> >>> >>> >> >> > > > ======================================================================= > This email, including any attachments, is only for the intended > addressee. It is subject to copyright, is confidential and may be > the subject of legal or other privilege, none of which is waived or > lost by reason of this transmission. > If the receiver is not the intended addressee, please accept our > apologies, notify us by return, delete all copies and perform no > other act on the email. > Unfortunately, we cannot warrant that the email has not been > altered or corrupted during transmission. > ======================================================================= > > > ------------------------------------------------------------------------ > ------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ---------------------------------------------------------------------------- -- > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > WiX-users mailing list > WiX-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wix-users > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > > ======================================================================= This email, including any attachments, is only for the intended addressee. It is subject to copyright, is confidential and may be the subject of legal or other privilege, none of which is waived or lost by reason of this transmission. If the receiver is not the intended addressee, please accept our apologies, notify us by return, delete all copies and perform no other act on the email. Unfortunately, we cannot warrant that the email has not been altered or corrupted during transmission. ======================================================================= ---------------------------------------------------------------------------- -- This SF.Net email is sponsored by the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
