<Upgrade Id="$(var.UpgradeCode)">
<UpgradeVersion Minimum="$(var.ProductVersion)" IncludeMinimum="no"
OnlyDetect="yes" Property="NEWERVERSION_INSTALLED" />
<UpgradeVersion Minimum="0.0.0" IncludeMinimum="yes"
Maximum="$(var.ProductVersion)" IncludeMaximum="no"
Property="OLDERVERSION_BEINGUPGRADED"
MigrateFeatures="yes" />
<UpgradeVersion Property="ANYVERSION" IncludeMinimum="yes"
Minimum="0.0.0.0" Maximum="99.99.99.99" IncludeMaximum="yes" OnlyDetect="yes" />
</Upgrade>
I'm going to reset the VM and try this again, as I feel I must be missing
something simple. (The logs would make sense if it's logging once per
<UpgradeVersion.../> element.) The behavior I was seeing is the MSI for the new
version wasn't executing.
-----Original Message-----
From: Rob Mensching [mailto:[email protected]]
Sent: Thursday, September 06, 2012 11:41 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn: WixStdBA and MajorUpgrade
What does your Upgrade table look like?
On Thu, Sep 6, 2012 at 7:40 AM, Hoover, Jacob <[email protected]>wrote:
> So I'm finally getting back to burn and I am running into a bit of
> confusion. Prior versions of my application were installed with
> DotNetBootstrapper as burn was still in its infancy. Now that 3.6 is
> official, I wanted to again look at burn and see if I could get a
> single polished UX. On a VM with just my old install in place when I
> attempt to run the install for the burn bundle, I get the following in the
> logs:
>
> [0CAC:0DAC][2012-09-06T09:06:45]: Detected related package:
> {9E551FB0-E250-4698-9145-FE615DC45805}, scope: PerMachine, version:
> 4.8.15.0, language: 0 operation: MajorUpgrade
> [0CAC:0DAC][2012-09-06T09:06:45]: Detected related package:
> {9E551FB0-E250-4698-9145-FE615DC45805}, scope: PerMachine, version:
> 4.8.15.0, language: 0 operation: Downgrade
>
> I've kept the UpgradeCode of the MSI the same and both the old and the
> new MSI's are configured for MajorUpgrades. I have no InstallCondition
> on my MsiPackage element. If I run the MSI outside of the BA, it
> properly removes the old MSI as expected. Is this a bug in WixStdBA or
> am I missing something on the <MsiPackage... /> element?
>
> Thanks,
> Jacob
>
>
> ----------------------------------------------------------------------
> --------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond.
> Discussions will include endpoint security, mobile security and the
> latest in malware threats.
> http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> WiX-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
--
virtually,
Rob Mensching
http://RobMensching.com LLC
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and threat
landscape has changed and how IT managers can respond. Discussions will include
endpoint security, mobile security and the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users