Well, aside from swapping left for right in the expression (a typical problem
for me). It just works, Some examples:
Product.wxs
http://schemas.microsoft.com/wix/2006/wi";>
I have some plugin DLLs, and for each plugin, there's an XML file
describing its IPC interface and an .ini file describing the plugin
configuration and location (required for the app to load the plugin).
Should I create three components? Or should they be in the same
component since the .ini file
John,
Your answer doesn't make sense to me. Can you check your syntax? I have tried
several ways to make sense out of your response but everything I try does not
build.
Best,
Robert
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Tuesday, July 1, 2014 3:32 P
Hello everyone,
I am really hoping you can help me as I'm at my wits end trying to get this
to work.
I have a Visual Studio sample project provided by a vendor that builds an
Internet Explorer BHO and installs it via Wix. The project is building
fine, but WIX does not build the installer.
Here
"FeatureA" ~>< FeatureList
The '~' makes the substring case insensitive.
--
John Merryweather Cooper
Build & Install Engineer - ESA
Jack Henry & Associates, Inc.®
Shawnee Mission, KS 66227
Office: 913-341-3434 x791011
jocoo...@jackhenry.com
www.jackhenry.com
-Original Message-
From: R
To Wix-Users,
I have a Burn bundle of Chained MSIs and I want to install one based on whether
or not a variable contains a specific word. I have variable I am setting from
the command line, ie Bundle.exe SelectedFeatures=. How do I set
the InstallCondition attribute on the MsiPackage element to
Hi John,
Thank your fort hat crucial hint. Before we started to version the helper
modules systematically with 1.0.x, the old version numbers on some but not all
modules were set to 1.4.0. So those dlls were not installed with the upgrade,
but since this happened simultaneously with the 2.0.x t
I should add that I provided a full path to an msi rather than just a file
name in SourceFile="a32.msi"
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7595606.html
Sent from the wix-u
I do not see any problem compiling this code against wix 3.8.1228 RTM
toolset.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/bootstrapperApplicationData-attribute-is-not-declared-tp7595444p7595605.html
Sent from the wix-users mailing list archive
If RadioButton1 is define as a numeric Engine variable, then use
'RadioButton1=1'. If RadioButton1 is defined as a string Engine variable
then test it against a string, i.e. 'RadioButton1="e;1"e;'
Either used html entities to put quotes around the string or use CDATA.
A Burn (Engine) var
Just another update for anyone in the future, the loc.blah variable I replaced
was in an older file we no longer use, so this wasn't the issue after all.
I now have a similar issue with candle 3.8 on windows 2012. This is obviously
not wide spread so must be down to our wix code, or maybe some t
11 matches
Mail list logo
