Nope... As far as I know, NOTHING will work in that scenario. AFAIK,
there's no way to handle this properly - you pretty much want to require
that users either only can install as Everyone, or only can install as
Just Me. Personally, I think "Just Me" is silly and can't come up with
any good reason for this installer choice.
Abubakar <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
11/26/2007 10:46 PM
To
"John Lalande" <[EMAIL PROTECTED]>
cc
wix-users@lists.sourceforge.net
Subject
Re: [WiX-users] uninstalling a product silently before installing a new
one
Thanks for the xml code, I have followed this and it is working in one
scenerio. But tell me, should this work if product1 was installed using
"just me" and the product2 is being installed using "Everyone"? Cuz i am
testing this and this the case in which my product1 is not getting
uninstalled.
..ab
On Nov 27, 2007 3:23 AM, John Lalande <[EMAIL PROTECTED]> wrote:
In theory (and in my projects), simply copy what you already have and
replace 'product2guid' (which I hope is a uuid), with the UpgradeCode of
the product you want uninstalled. In the new entry remove the
UpgradeVersion that uses the NEWERPRODUCTFOUND property and replace
PREVIOUSVERSIONSINSTALLED with something like OTHERPRODUCTFOUND or
whatever makes sense for you. Make sure that OnlyDetect is No.
I don't think you need the Property tags you have. They will be created
on demand and will be set to the ProductCode of the detected products.
Your updated Upgrade elements may look similar to this (adjust as
necessary):
<Upgrade Id="product2guid">
<UpgradeVersion Minimum="1.0.57" Property="NEWERPRODUCTFOUND"
OnlyDetect="yes" IncludeMinimum="yes" />
<UpgradeVersion Minimum=" 1.0.0.0" Maximum="1.0.57"
Property="PREVIOUSVERSIONSINSTALLED" IncludeMinimum="yes" />
</Upgrade>
<Upgrade Id="otherproductguid">
<UpgradeVersion Minimum="1.0.0.0" Maximum="1.0.57"
Property="OTHERPRODUCTFOUND" IncludeMinimum="yes" />
</Upgrade>
Finally, take heed of Christopher's comments as there are some subtleties
about individual file versions as well as where you have scheduled
RemoveExistingProducts.
Also, you may want to read the tutorial for more details on upgrades:
http://www.tramontana.co.hu/wix/lesson4.php.
Good luck.
John
On Nov 26, 2007 8:55 AM, Abubakar <[EMAIL PROTECTED]> wrote:
Hi, can you provide me the tags necessary to do this?
Right now my Upgrade tags look like this:
<Upgrade Id="product2guid">
<UpgradeVersion Minimum="1.0.57" Property="NEWERPRODUCTFOUND"
OnlyDetect="yes" IncludeMinimum="yes" />
<Property Id="NEWERPRODUCTFOUND" Secure="yes" />
<UpgradeVersion Minimum="1.0.0.0" Maximum="1.0.57"
Property="PREVIOUSVERSIONSINSTALLED" IncludeMinimum="yes" />
<Property Id="PREVIOUSVERSIONSINSTALLED" Secure="yes" />
</Upgrade>
regards,
..ab
On Nov 26, 2007 7:16 PM, John Lalande <[EMAIL PROTECTED]> wrote:
ab
It is much simpler then what you are proposing. Simply add the UpgadeCode
of the old product to the Upgrade table of your new product. The old one
will be uninstalled in the same manner as a previous version...silently
during the RemoveExistingProducts action.
John
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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 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: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
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
