Hi

you're right, thanks.

I used this:
    <bal:Condition Message="The Bootstrapper has to be installed in version
$(var.BaselineVersion)">
      (SampleMsiInstalledState = 5) AND (SampleMsiInstalledVersion &gt;=
v$(var.BaselineVersion))
    </bal:Condition>
    <util:ProductSearch Guid="my_samplePackMsi_guid" Result="version"
Variable="SampleMsiInstalledVersion" />
    <util:ProductSearch Guid="my_samplePackMsi_guid" Result="state"
Variable="SampleMsiInstalledState" />

do determine whether the previous servicePacked version of the msi in the
bundle was already installed. the SampleMsiInstalledState variable probably
isn't even needed.
The standard BA then also refused to install the bundle, no custom BA
necessary :)

What did not work was to use the bundle/@Condition attribute. When I used
that I only got "The specified program requires a newer version of
windows". xml documentation also says that burn built-in variables for OS
detection are used with this attribute.

Those helped:
http://stackoverflow.com/questions/16108405/wix-bundle-balcondition-utilregistrysearch-variable-always-false/16109285#16109285
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Burn-conditions-tt7580784.html#none

Took me a while to get the difference between the use case for
bundle/@Condition and bal:Condition.

Thanks for the help :)
Jakob


On Tue, Jun 18, 2013 at 10:44 AM, Blair Murri <os...@live.com> wrote:

> The standard BA supplied by WiX uses <bal:Condition> and evaluates it
> right after detection before planning. The one used to install the toolset
> also uses that same tag. You don't need a custom BA to use <bal:Condition>
> (although a custom BA would need to be coded to use it). A custom BA
> doesn't need <bal:Condition> (unless it deliberately chooses to support it).
>
> > From: subscr...@gmail.com
> > Date: Tue, 18 Jun 2013 08:20:06 +0200
> > To: wix-users@lists.sourceforge.net
> > Subject: Re: [WiX-users] prevent installation of bundle a bundle
> specific version is not installed
> >
> > I hoped that i didn't have to use a custom BA for things like that,
> because
> > like preventing the install of SP1FP1 without SP1 installed seemed to be
> > such a fundamental concept.
> >
> >
> > On Mon, Jun 17, 2013 at 11:08 PM, Blair Murri <os...@live.com> wrote:
> >
> > > would <bal:Condition/> work? A custom BA can always do whatever it
> wants
> > > in this area.
> > >
> > > Blair
> > >
> > > > From: subscr...@gmail.com
> > > > Date: Mon, 17 Jun 2013 11:54:54 +0200
> > > > To: wix-users@lists.sourceforge.net
> > > > Subject: [WiX-users] prevent installation of bundle a bundle specific
> > > version is not installed
> > > >
> > > > Hi all
> > > >
> > > > When we provide patch bundles for deployed service packs, the
> fixpacks
> > > only
> > > > contain the difference to the bundle ServicePack1.
> > > > Currently, the SP1 FixPack1 bundle installs also on systems where SP1
> > > doesn
> > > > not exist, leading to the msp patch not being installed (SP1
> missing),
> > > but
> > > > the bundle being installed.
> > > >
> > > > Is there a way to prevent a bundle to install if a given
> product/bundle
> > > > version does not exist on the system?
> > > > The Bunde/@Condition element seems to only support built-in
> variables and
> > > > can only be used to prevent installation on the wrong OS version.
> > > >
> > > > Cheers
> > > > Jakob
> > > >
> > >
> ------------------------------------------------------------------------------
> > > > This SF.net email is sponsored by Windows:
> > > >
> > > > Build for Windows Store.
> > > >
> > > > http://p.sf.net/sfu/windows-dev2dev
> > > > _______________________________________________
> > > > WiX-users mailing list
> > > > WiX-users@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> > >
> > >
> ------------------------------------------------------------------------------
> > > This SF.net email is sponsored by Windows:
> > >
> > > Build for Windows Store.
> > >
> > > http://p.sf.net/sfu/windows-dev2dev
> > > _______________________________________________
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> >
> ------------------------------------------------------------------------------
> > This SF.net email is sponsored by Windows:
> >
> > Build for Windows Store.
> >
> > http://p.sf.net/sfu/windows-dev2dev
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to