.... and something else to check is that InstallShield sometimes uses a thing 
called version lying. It's called "lying" because the File table in the MSI 
file gets a version of 65535.65535.... etc so it always replaces any existing 
file on the system. If you managed to transfer something like this into your 
WiX build you will replace that file. You'd need to look at the file table in 
your MSI file to see what version of mscomm32.ocx is in there. 

Phil Wilson 


-----Original Message-----
From: Blair [mailto:os...@live.com] 
Sent: Tuesday, January 12, 2010 3:34 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Windows System Folder

>From a debug-verbose installation log, what is the value of the
REINSTALLMODE property?

-----Original Message-----
From: Daniel Hughes [mailto:daniel.hug...@tait.co.nz] 
Sent: Tuesday, January 12, 2010 2:53 PM
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



*** Confidentiality Notice: This e-mail, including any associated or attached 
files, is intended solely for the individual or entity to which it is 
addressed. This e-mail is confidential and may well also be legally privileged. 
If you have received it in error, you are on notice of its status. Please 
notify the sender immediately by reply e-mail and then delete this message from 
your system. Please do not copy it or use it for any purposes, or disclose its 
contents to any other person. This email comes from a division of the Invensys 
Group, owned by Invensys plc, which is a company registered in England and 
Wales with its registered office at Portland House, Bressenden Place, London, 
SW1E 5BF (Registered number 166023). For a list of European legal entities 
within the Invensys Group, please go to 
http://www.invensys.com/legal/default.asp?top_nav_id=77&nav_id=80&prev_id=77. 
You may contact Invensys plc on +44 (0)20 7821 3848 or e-mail 
inet.hqhelpd...@invensys.com. This e-mail and any attachments thereto may be 
subject to the terms of any agreements between Invensys (and/or its 
subsidiaries and affiliates) and the recipient (and/or its subsidiaries and 
affiliates).



------------------------------------------------------------------------------
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

Reply via email to