; no problems.
>
> Wes
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: July-26-13 1:03 AM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall addon
> bundle on
13 1:03 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall addon bundle
on main bundle install
Actually, if your addon's aren't backwards compatible any longer it sounds like
you should change the addon related id
Am I abusing the addon feature?
>
> Wes
>
> -Original Message-
> From: Rob Mensching [mailto:r...@robmensching.com]
> Sent: July 25, 2013 5:46 PM
> To: General discussion for Windows Installer XML toolset.
> Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall
sching.com]
Sent: July 25, 2013 5:46 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Burn Addons - reevalulate and uninstall addon bundle
on main bundle install
Addons (and patch) bundles follow the main bundle (more written here:
https://support.firegiant.c
Addons (and patch) bundles follow the main bundle (more written here:
https://support.firegiant.com/entries/24024208-Bundle-chain-execution-order-).
To get the behavior you want, you'd need an upgrade relationship.
I think a custom BA could override the default behaviors without using an
upgrade r
I'm using wixstba and I have a addon bundle that I want to uninstall when a
certain version of my main bundle is installed (and prevent install if this
main bundle is present).
I'm using a registry search and bal:condition in the addon to do this. Looks
like the bal:condition does not do the
6 matches
Mail list logo
