[wix-devs] 6772 - ExePackage ARP entry

[Sean Hall]

I don't think that's a good idea. The correct way to do it is to get the
engine to detect the ExePackage as Obsolete in my scenario but Present in
yours and then it will work like all the other packages. That would require
the authoring to include a version range that is used to detect the
product. Absent is missing or less than the beginning of the range. Present
is inside of the range. Obsolete is greater than the end of the range.
That's basically what my original proposal was doing, but forced the user
to define the range in the DetectCondition.

On Wed, May 4, 2022 at 8:53 PM Bob Arnson <bob at firegiant.com> wrote:

> As long as a BA can override (to uninstall a package with a different
> version), +1.
>
> > -----Original Message-----
> > From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of Sean
> > Hall via wix-devs
> > Sent: Wednesday, 4 May, 2022 19:40
> > To: WiX Toolset Developer Mailing List <wix-devs at lists.wixtoolset.org>
> > Cc: Sean Hall <r.sean.hall at gmail.com>
> > Subject: Re: [wix-devs] 6772 - ExePackage ARP entry
> >
> > "My" scenario is multiple versions of the same product use the same ARP
> key.
> > When the bundle that has that package in an ExePackage is installed, the
> > ExePackage should only be installed if it's missing or there's an older
> version.
> > When the bundle is uninstalled, the ExePackage should only be
> uninstalled if that
> > exact version is installed.
> >
> > If you do the second part by itself, then it gets uninstalled when
> there's a
> > different version. The first part is also necessary.
> >
> > On Wed, May 4, 2022 at 6:15 PM Bob Arnson <bob at firegiant.com> wrote:
> >
> > > I considered the first part but settled for it being a rare-enough
> > > story that it could be handled in a BA. But the second part...well,
> > > that's interesting. I like that from the perspective of consistency
> > > with MsiPackage -- the ARP entry gives us the data we need for
> > > detection, just like the MSI API does for MsiPackage. I'm not seeing a
> > > downside; would that approach work for your scenarios?
> > >
> > > > -----Original Message-----
> > > > From: wix-devs <wix-devs-bounces at lists.wixtoolset.org> On Behalf Of
> > > > Sean Hall via wix-devs
> > > > Sent: Wednesday, 4 May, 2022 18:09
> > > > To: WiX Toolset Developer Mailing List
> > > > <wix-devs at lists.wixtoolset.org>
> > > > Cc: Sean Hall <r.sean.hall at gmail.com>
> > > > Subject: Re: [wix-devs] 6772 - ExePackage ARP entry
> > > >
> > > > It's either that or we have to add a new way to prevent
> > > > uninstallation
> > > when it's
> > > > detected as present, in which case the presence of the ARP entry
> > > > could
> > > replace
> > > > the DetectCondition and we don't have to create the version variable.
> > >
> > _________________________________________________________________
> > ___
> > WiX Toolset Developer Mailing List provided by FireGiant
> > http://www.firegiant.com/
>