i think i misundestand something in wix philosophy.
I have 4 exe to install. I've created a bundle and 4 fragments.
All is working nicely.
Now i want to conditonally add a registry key when one of the fragment is
"executed".
So i added this to the fragment:
<DirectoryRef Id="TARGETDIR"> <Component Id="RegistryEntries"
Guid="*"> <Condition><![CDATA[NETFRAMEWORK40CLIENT AND
(VersionNT < v6.0)]]></Condition> <RegistryKey Root="HKCU"
Key="Software\Company\ProductName" Action="create">
<RegistryValue Type="integer" Name="State" Value="1" KeyPath="yes" />
</RegistryKey> </Component> </DirectoryRef>
<Feature Id="NetFx40ClientWebSupplement"> <ComponentRef
Id="RegistryEntries" /> </Feature>
But I don't know how to reference the feature, as i only have a bundle, not
a product.
Why would i do that ?
I'm trying to detect in the managed bootstrapper if the prerequisite
bootstrapper installed the .net framework or not (which is different of
detecting if .net is installed).
Why would i do that ?
Because i'm trying to find a way to detect if another install is already in
progress and requires a reboot. the only way i have found is read the
PendingFileRenameOperations key. But the prerequisite bootstrapper sets
this key after strarting the managed bootstrapper ...
I'm stuck.
2013/5/29 John Ludlow <john.ludlow...@gmail.com>
> Well, the bundle will *take any MSIs or other packages specified in your
> Chain element** *and bootstrap them. It doesn't exactly create an MSI
> itself.
>
> It might be best if you give more details about what you're trying to
> achieve, and where you're trying to use the above Condition element?
>
>
> On 29 May 2013 11:36, Benjamin Mayrargue <benja...@vapolia.fr> wrote:
>
> > 100% understood !
> >
> > This means a 'bundle' creates a msi bootstrapped in an exe.
> >
> > B.
> >
> >
> >
> > 2013/5/29 John Ludlow <john.ludlow...@gmail.com>
> >
> > > I think where you're getting confused is that there are more than one
> > type
> > > of "variable" in WiX. Firstly, there are preprocessor variables and
> > > condition, which are referenced like this:
> > >
> > > $(var.VariableName)
> > > !(var.LateBoundVariableName)
> > > $(env.EnvironmentVariableName)
> > > !(loc.StringID)
> > >
> > > These are available at build time and are used in things like string
> > paths
> > > and to conditionally include fragments of code based on your build
> > > configurations. (Check out this link:
> > > http://wix.sourceforge.net/manual-wix3/preprocessor.htm)
> > >
> > > Then there are the MSI properties and conditions, which use a different
> > > syntax, because it's defined by MSI and not WiX. These are avaiable at
> > > runtime and are used to perform logic in your install - conditionally
> > > performing an action based on the environment or feature selection,
> > getting
> > > information, controlling your installation directories and stuff like
> > that.
> > > (Check out this link:
> > >
> > >
> >
> http://msdn.microsoft.com/en-us/library/windows/desktop/aa368012(v=vs.85).aspx
> > > )
> > >
> > > What you have there is an MSI condition, which looks like it's based on
> > > MainFeature being installed. To break this down:
> > >
> > > (&MainFeature = 3)
> > >
> > > &FeatureName gets the requested state of the feature. &MainFeature = 3
> > > means "if MainFeature is selected for installation, return true".
> > >
> > > AND NOT
> > >
> > > Pretty standard boolean logic - if the left hand side is true, but the
> > > right hand side is false, this will return true.
> > >
> > > (!MainFeature = 3)]
> > >
> > > !FeatureName gets the *current state* of the feature, rather than the
> > > requested state. This means "if MainFeature is *currently installed*
> for
> > > installation, return true".
> > >
> > > Put it all together, and what you get is this: "If MainFeature is
> > selected
> > > for installation, and it's NOT currently installed, return true".
> > >
> > > Hope that helps
> > >
> > >
> > > On 29 May 2013 09:46, Benjamin Mayrargue <benja...@vapolia.fr> wrote:
> > >
> > > > Hi all,
> > > > i have a noob question.
> > > >
> > > > In this snippet there is a & and a ! before the variable MainFeature.
> > > > what does that mean ?
> > > >
> > > > <Condition><![CDATA[(&MainFeature = 3) AND NOT (!MainFeature =
> > > > 3)]]></Condition>
> > > >
> > > > In the wix chm, i found the list of "Wix built-in variables.
> > > > But i'm unable to reference them, either in the bundle, or in my
> > managed
> > > > bootstrapper. What is the correct way to make them available ? (i'm
> > using
> > > > only a bundle).
> > > >
> > > > thks :)
> > > >
> > > >
> > >
> >
> ------------------------------------------------------------------------------
> > > > Introducing AppDynamics Lite, a free troubleshooting tool for
> Java/.NET
> > > > Get 100% visibility into your production application - at no cost.
> > > > Code-level diagnostics for performance bottlenecks with <2% overhead
> > > > Download for free and get started troubleshooting in minutes.
> > > > http://p.sf.net/sfu/appdyn_d2d_ap1
> > > > _______________________________________________
> > > > WiX-users mailing list
> > > > WiX-users@lists.sourceforge.net
> > > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > > >
> > >
> > >
> >
> ------------------------------------------------------------------------------
> > > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> > > Get 100% visibility into your production application - at no cost.
> > > Code-level diagnostics for performance bottlenecks with <2% overhead
> > > Download for free and get started troubleshooting in minutes.
> > > http://p.sf.net/sfu/appdyn_d2d_ap1
> > > _______________________________________________
> > > WiX-users mailing list
> > > WiX-users@lists.sourceforge.net
> > > https://lists.sourceforge.net/lists/listinfo/wix-users
> > >
> >
> >
> ------------------------------------------------------------------------------
> > Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> > Get 100% visibility into your production application - at no cost.
> > Code-level diagnostics for performance bottlenecks with <2% overhead
> > Download for free and get started troubleshooting in minutes.
> > http://p.sf.net/sfu/appdyn_d2d_ap1
> > _______________________________________________
> > WiX-users mailing list
> > WiX-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/wix-users
> >
>
> ------------------------------------------------------------------------------
> Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
> Get 100% visibility into your production application - at no cost.
> Code-level diagnostics for performance bottlenecks with <2% overhead
> Download for free and get started troubleshooting in minutes.
> http://p.sf.net/sfu/appdyn_d2d_ap1
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
