[wix-users] SuppressDowngrade still installs a bundle

[Sean Hall]

I don't know why it continues to go through the plan/execute phases, that
seems like a reasonable feature request.

The documentation probably said "successful do-nothing operation" because
the Burn engine won't try to install a package if it is detected as Present
or Obsolete or Superseded, which is what's supposed to happen when you're
downgrading a bundle. If no packages are planned to be installed then the
execute phase shouldn't register the bundle. You would have to provide the
full log for us to know why you're getting a side-by-side install.

On Wed, Jul 7, 2021 at 3:58 PM Jacques Eloff <repstosd at gmail.com> wrote:

> Hi Sean
>
> This is a bundle that ships through WSUS. WSUS differentiates between
> security and non-security updates, which can sometimes result in offering
> older releases depending on how customers configure their update policies.
> In those cases we want to avoid seeing downgrade failures when a deployment
> runs over thousands of machines in an enterprise environment.
>
> I read the documentation and it sounded like it was exactly what we
> wanted. This was the cheaper option to implement and something we've used
> in custom chainers previously.
>
> I understand that it's by design and just wanted to confirm.
>
> Thanks,
> Jacques
>
> On Wed, Jul 7, 2021 at 1:34 PM Sean Hall via wix-users <
> wix-users at lists.wixtoolset.org> wrote:
>
>> That documentation doesn't match the commit message (
>>
>> https://github.com/wixtoolset/codeplex/commit/2222d3e0e988763b3a46d07583acfd5046949e36
>> ):
>>
>> Add bal:WixStandardBootstrapperApplication/@SuppressDowngradeFailure to
>> let
>> attempted downgrades happen. This is useful for redistributable bundles
>> where a later version major-upgrades prior versions and where a product
>> that ships with a prior version shouldn't cause an error when a later
>> version of the redistributable is already present.
>>
>> Why do you want your bundle to return success if someone tries to install
>> an older version than the one that is already installed? Don't you want
>> the
>> user to know that it failed to install in that case?
>>
>> On Wed, Jul 7, 2021 at 12:35 PM Jacques Eloff via wix-users <
>> wix-users at lists.wixtoolset.org> wrote:
>>
>> > Hi
>> >
>> > Reading through the documentation, the BAL extension to suppress
>> downgrades
>> > in the bootstrapper states that when set to "yes", it should result in a
>> > "successful, do-nothing" operation.
>> >
>> > However, when I create two upgrade related bundles with the success
>> > blocker, it actually continues to execute the downgrade and I end up
>> with a
>> > SxS install of the two bundles.
>> >
>> > [01BC:1E74][2021-07-07T09:03:43]i000: A newer version of this product is
>> > installed but downgrade failure has been suppressed; continuing...
>> > [01BC:2F48][2021-07-07T09:03:43]i200: Plan begin, 3 packages, action:
>> > Install
>> >
>> > I was expecting that the plan/execute phases would be skipped, but that
>> > does not appear to be the case?
>> >
>> > Do I need to add conditions on the packages to check if a downgrade is
>> in
>> > progress? Does WiXBundleAction support detecting downgrades?
>> >
>> > Thanks,
>> > Jacques
>> >
>> > ____________________________________________________________________
>> > WiX Toolset Users Mailing List provided by FireGiant
>> > http://www.firegiant.com/
>> >
>>
>> ____________________________________________________________________
>> WiX Toolset Users Mailing List provided by FireGiant
>> http://www.firegiant.com/
>>
>