There's a MSI that I don't control that needs to be added into a Bundle.
This MSI needs some settings in place before install. It also needs these
settings removed before the MSI uninstalls in order to know that it should
be uninstalling.
That's why I need that MSI to always install/uninstall af
Burn doesn't support that. What is the underlying requirement? I've never
heard the need for such complexity.
On Wed, Sep 5, 2012 at 3:02 PM, Adam Westhusing wrote:
> I've got a bundle that contains 3 MSIs (A, B, and C). I want one MSI (A)
> to
> always install and uninstall after another one (B
I've got a bundle that contains 3 MSIs (A, B, and C). I want one MSI (A) to
always install and uninstall after another one (B).
The After attribute works on install (A properly installs after B), however
on uninstall I want A to uninstall after B as well but Burn always runs the
Chain in reverse
3 matches
Mail list logo
