Thanks guys! Got it now. Much appreciated.
________________________________
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Wilson,
Phil
Sent: den 27 maj 2008 18:34
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Automatic major upgrade installation of
application
I'll add:
ALLUSERS must be same.
And pick a nit:
ProductVersion must be incremented somewhere in its first three fields.
Phil Wilson
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Alex
Goryuk
Sent: Tuesday, May 27, 2008 5:41 AM
To: wix-users@lists.sourceforge.net
Cc: Holmgren Mathias
Subject: Re: [WiX-users] Automatic major upgrade installation of
application
Major upgrades require primarily the following things:
http://msdn.microsoft.com/en-us/library/aa370579(VS.85).aspx
* ProductCode changed
* ProductVersion changed
* UpgradeCode being the same between the two installers
* an Upgrade element in the installer (.wxs) that can allow the major
upgrade to happen ( this populates the "Upgrade" table in the built MSI
)
The example can be found here:
http://www.tramontana.co.hu/wix/lesson4.php
Alex G.
On 5/27/08 7:43 AM, "Holmgren Mathias" <[EMAIL PROTECTED]> wrote:
I have a question about automatic application upgrades.
I have a WiX 3.0 MSI file that installs version 3.0 of an application.
I want MSI to detect if a previous version of the application is
installed and if so, remove the previous installation (2.0) before the
new version (3.0) is installed.
Between version 2.0 and 3.0 there have been component changes and the
application has undergone some significant changes, so major upgrade
makes sense to me.
So far both versions of the application installs with the same
UpgradeCode. Since it is a major upgrade version 3.0 has a new
ProductCode (<Product Id="...") that is different from the in the 2.0
installer. In version 3.0 I also set the product version to the EXE file
version using <Product ... Version="!(bind.FileVersion.TheExeFileId)">.
But it is not enough. Currently version 3.0 installs happily side by
side with version 2.0, which is not what I want. Also, if I install a
new build of 3.0 over a previous build of 3.0 Windows Installer
complains and tells me I have to uninstall the previous version of 3.0
first.
Obviously I have to somehow tell Windows Installer to treat the
installation as an upgrade. I have tried reading up on revision numbers
and type of upgrades, but I still don't know what I'm supposed to do.
I want it to be automatic that the previous version is always
uninstalled
before the new version is installed.
Is this possible in both my two upgrade cases?
* 2.0 -> 3.0
* 3.0.build -> 3.0.build+1
What do I need to do/learn to accomplish this?
PS. I am using VS2005 with SP1, .NET FW 1 with SP1 and WiX 3.0.
/Mathias
________________________________
------------------------------------------------------------------------
-
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
________________________________
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
