Yes, that's because it includes the Upgrade table with the appropriate
version-detection information, and schedules the RemoveExistingProducts
action.

 

If you want to do the same with WiX, you'll have to do it by hand. There are
consequences to where you schedule RemoveExistingProducts.

 

It can be educational to view an existing MSI in the Orca editor (part of
the Platform SDK) and, if trying to learn Windows Installer properly after
having used VS Setup & Deployment projects, to read Phil Wilson's book "The
Definitive Guide to Windows Installer".

 

-- 

Mike Dimmick

 

  _____  

From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rory Clark
Sent: 17 May 2007 18:39
To: Brian Simoneau; wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Making upgrades work without the msiexec
commandlines?

 

I used to have a Visual Studio Setup project a number of years ago, VS.Net,
that I was able to build the MSI's for that didn't require an uninstall to
install a more recent version of the MSI by double clicking on the generated
MSI.

 

Thanks!

Rory

 

  _____  

From: Brian Simoneau [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 17, 2007 9:51 AM
To: Rory Clark; wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] Making upgrades work without the msiexec command
lines?

I think this is wishful thinking.  A minor upgrade is going to require
command line parameters for msiexec.

 

-Brian Simoneau

-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Rory Clark
Sent: Thursday, May 17, 2007 12:18 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Making upgrades work without the msiexec command lines?

I have a wxs script to build an MSI with a product node that looks something
like this:

    <Product Name="Some App" 

             Id="C1226E59-7817-4A47-BAEF-2DF94362872F" 

             UpgradeCode="ADD87970-F3CC-40f3-9454-28871A017FEC"

             Version="2.0.0" 

             Manufacturer="InfoSpace, Inc." 

             Language="1033">

        <Package Id="????????-????-????-????-????????????" 

                 Comments="Installs Some App on the target machine." 

                 Description="Description of Some App" 

                 Manufacturer="InfoSpace, Inc." 

                 InstallerVersion="200" 

                 Languages="1033" 

                 Compressed="yes" />

 

 

If I previously installed version 2.0.0 on the box and then change the
version number to 2.0.1 and then double click on the MSI, I get the "please
uninstall the old version first" message.

 

Is there a way to make it so I don't have to run msiexec.exe with the
command line switches to do an upgrade?

 

I tried varying the UpgradeCode, and that didn't work and that the same
message.

 

If I varied the Id in Product, I would get two entries in Add/Remove
programs rather than one and the later one lays down files over the earlier.

 

Any thoughts on this?  Is it wishful thinking?

 

Thanks!
Rory

 

 

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to