al
> error) .
>
> Also, for most teams after picking baseline source code for their BA the
> UI is easier to maintain for a bundle than it is for MSIs (another plus
> once you've taken the initial cost).
>
> Blair
>
> > From: rhal...@hotmail.com
> > To: wix-
te: Fri, 5 Jul 2013 19:04:16 -0500
> Subject: Re: [WiX-users] Removing bundle after installing MSI's
>
> I think what you're missing is that you're assuming every package in the
> chain has a user interface. My typical installer has my application MSI, and
> at least on
dify the engine to do this?
Sean
> From: r...@robmensching.com
> Date: Fri, 5 Jul 2013 14:04:28 -0700
> To: wix-users@lists.sourceforge.net
> Subject: Re: [WiX-users] Removing bundle after installing MSI's
>
> I don't understand the reasoning here "I''m
wo?
Bill
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Sent: Friday, July 5, 2013 5:04 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Removing bundle after installing MSI's
I don't understand the reasoning her
I don't understand the reasoning here "I''m unwilling at this point to let
the bundle take over the handling of the MSI". What is the real difference
between having the Bundle registered as the ARP entry vs. the MSI
registered as the ARP entry?
Random note: Burn will clean up the package cache dur
I was faced with the same dilemma. I wanted to simply use the bundle to pave
the way for my main MSI.
As it is I've set the Permanent & Visible attribute of all the Package elements
in the bundle to "yes".
Thus when the bundle is finished it has an entry in the ARP but uninstalling it
essentiall
6 matches
Mail list logo
