Marc, I concur with Brian, but make sure you have your AppSearch sequenced
somewhere before your RemoveExistingProducts in this case, or else MSI
will remove the existing version before you get a chance to search the
registry for the item. BTW, if you have already released 1.0 and you
can't "add" the registry item, another type of AppSearch may work, like a
file system search, for instance, or you may need a CA to do this. You
could also write a CA (or there may support for this already in MSI's
AppSearch) to read from the existing component location of one of your
'always installed' components of your previous MSI.
Kelly
"Brian Simoneau" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/02/2007 06:36 AM
To
"Marc Scheuner" <[EMAIL PROTECTED]>, <wix-users@lists.sourceforge.net>
cc
Subject
Re: [WiX-users] The whole update maze in MSI
To get the second option to work, save the installation directory in the
registry when you install v1.0. Then when performing a major upgrade,
have v1.1 search the registry for the installation directory and use it.
-Brian Simoneau
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Marc
Scheuner
Sent: Friday, November 02, 2007 7:29 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] The whole update maze in MSI
Folks,
I'm trying to do this:
* Install MyApp v1.0 into a custom directory (e.g. X:\wacky\weirdo\MyApp)
* Later, install an update (to v1.01 or v1.1) that picks up where my v1.0
is installed and goes to the same directory by default
I figured since not a whole lot has changed between 1.0 and 1.1, I'd use
the same ProductID and do a minor update - trouble is, I can't seem to get
this to work so that I can just double-click on the Myapp_v1.1.msi and
have it run, uninstall the previous v1.0 version, and install itself into
that custom directory the user had picked.
So I chose to use a Major update, since in that case, I can get it to work
as expected (just double-click the MSI and off you go), but in that case,
I can't seem to "save" the installation directory for v1.0 long enough so
that v1.1 will pick up on it. v1.0 gets uninstalled okay, but the MSI
insists on putting v1.1 into the default directory (c:\program
files\[manufacturer]\MyApp11 or whatever it is).
So how do I
* either make MINOR updates WORK automagically without a plethora of
commandline switches - just double-click on the v1.1 MSI and off you go
and MyApp is updated
* get the MAJOR update to work so that when installing v1.1, I can somehow
find the installation directory for v1.0 before it gets uninstalled, and
use it as the default for my update-install for v1.1
I've read and re-read and re-re-read the MSI docs and all the web site and
tutorial and books I can get on MSI and its update magic - I don't get it.
Can one of you help? Have you done this, and how?
Cheers ! Marc
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
**************************************************************************************
This communication is intended solely for the addressee and is
confidential. If you are not the intended recipient, any disclosure,
copying, distribution or any action taken or omitted to be taken in
reliance on it, is prohibited and may be unlawful. Unless indicated
to the contrary: it does not constitute professional advice or
opinions upon which reliance may be made by the addressee or any
other party, and it should be considered to be a work in progress.
Unless stated otherwise, this communication does not form a prescribed
statement of actuarial opinion under American Academy of Actuaries
guidelines.
**************************************************************************************
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
