I'm trying to upgrade a previous version of our product with Burn. I have a
bundle that contains 4 MSIs and have already successfully put together a
bundle that upgraded from a previous one (Ex. upgrading 2.0 to 2.0.1)
I'm trying to upgrade our product from 2.0.1 to 2.1 and I'm running into an
e
I have this same problem, but Windows Update works on the machine and the
machine is up-to-date as far as updates go.
Is there some way to turn on or off this automatic updating mechanism? What
is generating that error?
--
View this message in context:
http://windows-installer-xml-wix-toolset
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
? 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).
>
4 matches
Mail list logo
