YES! The custom actions for setting an upgrade code for each instance could
be resolved by having an UpgradeCode attribute in the InstanceTransform
element. :D
However, unless there is something I am missing with multi-instance major
upgrades, I would still need the custom action that updates the
? E-Mail Me
From: Tyler Walters tyler.walters...@gmail.com
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Sent: Monday, April 18, 2011 10:18 AM
Subject: Re: [WiX-users] Multi-Instance Major Upgrades
YES! The custom actions for setting an upgrade code
Could all of the custom actions have been avoided if the InstanceTransform
element provided the ability to specify a unique UpgradeCode?
On Fri, Apr 15, 2011 at 7:54 AM, Tyler Walters
tyler.walters...@gmail.comwrote:
FINALLY! And naturally it didn't end up being very complicated. :p
So here
FINALLY! And naturally it didn't end up being very complicated. :p
So here is what i did.
1. In my .wxs I made an upgrade element to upgrade the product like you
normally would EXCEPT I made the upgrade code a random guid (NOT one i am
using). This was the only way I could get wix to
If you want to avoid having to make a bogus upgrade element just use the
EnsureTable element for the Upgrade table. Then you would be able to add
your custom rows with no problems (since the empty table will be in the
MSI).
--
View this message in context:
Oh cool! Thanks. I hadn't come across that one.
On Fri, Apr 15, 2011 at 12:56 PM, jhennessey jack.hennes...@hyland.comwrote:
If you want to avoid having to make a bogus upgrade element just use the
EnsureTable element for the Upgrade table. Then you would be able to add
your custom rows with
Currently I can do a major upgrade of a specific instance. There are a
couple problems though.
1. The default instance is upgraded fine. The transforms are upgraded,
BUT the previous version is not removed. So they both show up in ARP.
2. I need to be able to not downgrade a specific
Tyler,
Problem 1 - In order for a major upgrade to work, you have to call
RemoveExistingProducts to remove older versions. Given your post, I
don't see that in your execute sequence.
Problem 2 - I can't offer any advice for that, sorry.
Chris
On 04/14/2011 12:35 PM, Tyler Walters wrote:
RemoveExistingProducts is part of the MajorUpgrade element. The Schedule
attribute is what schedules RemoveExistingProducts.
Thanks for the advice though.
I am thinking I may have to do a custom action that modifies the
UpgradeTable at install time, if that is even possible.
On Thu, Apr 14,
9 matches
Mail list logo
