[wix-users] MSI vs. Bootstrapper

[Ondrej Krc-Jediny]

I have Compressed=yes already and also Visible=No (which I do not set
explicitly, but it is the default). We ship both .msi and bootstrapper .exe
to the customers intentionally, that's why I'm thinking of such scenarios.

On Mon, Jun 27, 2016 at 10:31 AM, Farrukh Waheed <farrukh1 at gmail.com> wrote:

> 1. Just my guess. You are not compressing .msi into your Bootstrapper.exe
> i.e. In your Chain, MsiPackage's attribute 'Compressed' should be 'yes' and
> Visibile should be 'no'. So better compress msi into Bootstrapper.exe and
> let your customers do the Install/Uninstall things from Boostrapper.exe.
> Visible='no' would present it to appear in Control Panel
>
> 2.Not sure how you are handling Major Upgrade. But first implement 1, which
> may solve issue 2 as well.
>
> On 27 June 2016 at 12:16, Ondrej Krc-Jediny <ondro.krc at gmail.com> wrote:
>
> > 1. I don't. But customers accidentally might use bootstrapper over .msi
> > installation and I would like to handle such scenarios correctly.
> > 2. Yes my bootstrapper is managed. The way I understand it, the product
> is
> > correctly major-upgraded (previous version is uninstalled before new
> > version is upgraded), the only problem is an 'empty' bootstrapper
> > registered in ARP. When I launch uninstall on it, it uninstalls
> immediately
> > and I am left with correct .msi upgraded installation.
> >
> > On Fri, Jun 24, 2016 at 5:18 PM, Farrukh Waheed <farrukh1 at gmail.com>
> > wrote:
> >
> > > 1: Why do you need to Repair it with Bootstrapper, when you can repair
> it
> > > with the msi or from Program & Features directly?
> > > 2. Seems like your Major upgrade is not uninstsalling previous version
> > > before installing its upgraded version. Is your bootstrapper a Managed
> > > Bootstrapper?
> > >
> > > On 24 June 2016 at 15:44, Ondrej Krc-Jediny <ondro.krc at gmail.com>
> wrote:
> > >
> > > > Hello,
> > > > I'd like to ask two questions. It is possible that customers for our
> > > > product will use both managed bootstrapper installer and .msi.
> > > >
> > > > 1:
> > > > When I install the product with .msi and Repair it with bootstrapper,
> > it
> > > > results in two ARP entries (one for the bootstrapper, one for the
> > > 'visible'
> > > > .msi).
> > > > Is there any way I can hide the .msi ARP entry after such operation?
> > > >
> > > > 2:
> > > > When I install the product with bootstrapper and do a Major Upgrade
> > with
> > > > .msi, it results in two ARP entries.
> > > > Is there any way I can unregister the bootsrapper?
> > > > The only way I can think of is to call a command that is called when
> > > > bootstrapper is major upgraded with another bootstrapper to
> unregister
> > > the
> > > > old one:
> > > > "C:\ProgramData\Package Cache\{BUNDLE_PRODUCT_CODE}\Bootstrapper.exe"
> > > > -uninstall -quiet -burn.related.upgrade -burn.ancestors={SOME_GUID}
> > > > But I don't know to find out the BUNDLE_PRODUCT_CODE and SOME_GUID
> > inside
> > > > the .msi.
> > > >
> > > > Thank you for your help
> > > >
> > > > ____________________________________________________________________
> > > > WiX Toolset Users Mailing List provided by FireGiant
> > > > http://www.firegiant.com/
> > > >
> > >
> > > ____________________________________________________________________
> > > WiX Toolset Users Mailing List provided by FireGiant
> > > http://www.firegiant.com/
> > >
> >
> > ____________________________________________________________________
> > WiX Toolset Users Mailing List provided by FireGiant
> > http://www.firegiant.com/
> >
>
> ____________________________________________________________________
> WiX Toolset Users Mailing List provided by FireGiant
> http://www.firegiant.com/
>