My inclination would be to do a major upgrade each time, sequencing
RemoveExistingProducts to uninstall the old app first then install the
updated one.
The issue with REINSTALLMODE is that it applies to every file in the
product, and I'm assuming you don't want to use (say)
REINSTALLMODE=vamus to force *every* file to replaced no matter what.
A companion file would work but yes it's tedious. It might in fact be
*less* tedious if you used Visual Studio to open up the code files and
add an appropriate version. Or you could automate this by
copying/inserting a resource/version from a file with the "right"
version using the resource APIs.
Version lying has the issue that the version you install on the system
is not the same as the version in the MSI's File table, and I believe
the MSI team has advised against it for this reason - the product could
be treated as broken because of that mismatch and a repair will never be
able to correct it.
Phil Wilson
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of John
Ludlow
Sent: Monday, December 11, 2006 3:35 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Fwd: How can I force files to be overwritten?
---------- Forwarded message ----------
From: John Ludlow <[EMAIL PROTECTED]>
Date: Dec 11, 2006 11:34 PM
Subject: Re: [WiX-users] How can I force files to be overwritten?
To: Scott Palmer <[EMAIL PROTECTED]>
You need to look into the REINSTALLMODE property (
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/set
up/reinstallmode.asp
<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/se
tup/reinstallmode.asp> ). This property controlls how MSI interprets
the versioning rules.
I believe another way is to set the file version to something very high,
so it will be overwritten in any situation. (This isknown as "version
lying" since you're essentially lying about the file version). I think
you can use the DefaultVersion attribute for this. However, I've never
got this working very welll...
On 12/11/06, Scott Palmer <[EMAIL PROTECTED] > wrote:
I have several files from a third party that I can not control
the version information in. It may be that the version information is
set to 1.0.0.0 <http://1.0.0.0/> for different versions of the same
file, some files have no version info at all. I want to be sure that
the latest file gets installed even if the previous version is already
in place. This doesn't seem to be the case currently, which results in
a mix between version A and version B of this framework. Obviously that
causes a problem. Is there an easy way to get the MSI to do the right
thing? My first guess is that I might be able to use the CompanionFile
attribute.. but that is going to be a very tedious thing to set up. I'm
not even sure if CompanionFile can refer to files in other components,
as it isn't mentioned in the WiX docs.
Scott
------------------------------------------------------------------------
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance
to share your
opinions on IT & business topics through brief surveys - and
earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDE
V
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
