Not too bothered about 3 so I'll ignore it for now. Just mentioned it as one 
our QA guys noticed it today.

Regarding 4, I do have the same product code & higher version however my 
Upgrade Table code looks like the following:

    <Upgrade Id="removed">
      <!--Original Shared Content UpgradeCode reinstated. This should never 
change-->
      <UpgradeVersion Minimum="2.2.0" IncludeMinimum="yes" OnlyDetect="yes" 
Property="NEWERVERSIONDETECTED" />
      <UpgradeVersion Minimum="1.0.0" IncludeMinimum="yes" Maximum="1.9.9" 
IncludeMaximum="yes" IgnoreRemoveFailure="no" OnlyDetect="no" 
Property="OLDERVERSIONBEINGUPGRADED" />
    </Upgrade>

Burn is trying to be too clever for its own good & changing the expected 
behaviour. I create a patch to upgrade from 2.0 or 2.1 to 2.2 as it's less than 
half the size of the full installer & I don't want to make users download 
something they don't need.
Forcing someone to use a Minor Upgrade when they actually want either Major 
Upgrade or disallow installation seems rather counter-intuitive.

I'll raise bugs in the SourceForge tracker for the other issues.

Palbinder Sandher 
Software Platform Engineer 
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com 

**Design, Simulate + Innovate with the <Virtual Environment>** 
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20 
0SP
Email Disclaimer 



-----Original Message-----
From: Rob Mensching [mailto:r...@robmensching.com] 
Sent: 26 April 2012 15:41
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to false, 
attempts minor upgrade

1. Agree about the InstallCondition doc. Want to file a bug?
2. DisplayInternalUI on MSP might be broken. Want to file a bug?
3. Burn calculates size of installed packages + their cache size if they
are cached. I'd need more details about the size being wrong to be more
helpful.
4. The log file should explain when an MSI is being minor upgraded.
Basically, if you have same product code but higher version, minor upgrade
kicks in.

On Thu, Apr 26, 2012 at 3:11 AM, Pally Sandher <pally.sand...@iesve.com>wrote:

> I've removed the InstallCondition for the patch & it's now working as
> intended. Thanks for the input on this however I would point out the
> documentation mentions nothing about "patch applicability" & the
> InstallCondition description says "A condition to evaluate before
> installing the package. The package will only be installed if the condition
> evaluates to true." which it's not unreasonable to assume the converse
> (i.e. if InstallCondition evaluates to false, the package is not installed)
> -> http://wix.sourceforge.net/manual-wix3/wix_xsd_msppackage.htm
>
> Anyone have any input on the previous questions I posted in this thread?
> Why is DisplayInternalUI="yes" being ignored for MspPackage. Also
> InstallSize seems to be ignored in MspPackage & ExePackage (tried setting
> it to 0 and 1, same results with burn size entry in ARP showing the total
> of all packages in the chain which is vastly inflated).
>
> My original question is still unanswered. Even without an InstallCondition
> attribute for the MsiPackage it will still attempt a minor upgrade which is
> contrary to the behaviour it exhibits when the MSI is manually run.
>
> Palbinder Sandher
> Software Platform Engineer
> T:+44 (0) 141 945 8500
> F:+44 (0) 141 945 8501
> http://www.iesve.com
>
> **Design, Simulate + Innovate with the <Virtual Environment>**
> Integrated Environmental Solutions Limited. Registered in Scotland No.
> SC151456
> Registered Office - Helix Building, West Of Scotland Science Park, Glasgow
> G20 0SP
> Email Disclaimer
>
>
> -----Original Message-----
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: 26 April 2012 06:51
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn - MSIPackage InstallCondition evaluates to
> false, attempts minor upgrade
>
> Sounds like we should scan patches for those that disallow removal and mark
> them permanent.
>
> The InstallCondition behavior is expected. If the InstallCondition is false
> that means "this Package should not be Installed" (aka: should not exist on
> the box).
>
> On Wed, Apr 25, 2012 at 9:30 AM, Bob Arnson <b...@joyofsetup.com> wrote:
>
> > On 25-Apr-12 10:06, Pally Sandher wrote:
> > > Why is it attempting to uninstall the patch when the condition is
> false&
> >  the patch has AllowRemoval="no"?
> > Because Burn always attempts to uninstall a package that's present when
> > its install condition is false, and Burn doesn't know the patch is
> > permanent. You can file a feature request to change either of those
> > facts or consider using patch applicability instead of install
> > conditions to control the patch installation.
> >
> > --
> > sig://boB
> > http://joyofsetup.com/
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > 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
> > WiX-users@lists.sourceforge.net
> > 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
> WiX-users@lists.sourceforge.net
> 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
> WiX-users@lists.sourceforge.net
> 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
WiX-users@lists.sourceforge.net
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
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to