FWIW, you don't need the AND NOT clause in your InstallCondition. If the
DetectCondition is true, Burn knows it doesn't need to install it. The
InstallCondition at that point can only uninstall the package.
FireGiant | Dedicated
During an administrative installation, the installer creates a source image for
all features in the product except those feature with 0 in the Level column of
the Feature table.
The pre-req bootstrapper only kicks in if the managed bootstrapper application
can't be loaded. If it can, it doesn't evaluate pre-req packages.
FireGiant | Dedicated support for the WiX toolset |
FireGiant | Dedicated support for the WiX toolset |
From: Phill Hogland [mailto:phogl...@rimage.com]
Sent: Friday, 24 April, 2015 17:46
On 18-Mar-15 14:13, Phill Hogland wrote:
I moved my mba from NetFx40WebClient to NetFx451Web. Previously I did not
run into the errors related to WixMbaPrereqPackageId and
WixMbaPrereqLicenseUrl, as they are defined in NetFx40.wxs. Since they are
not defined in NetFx451.wxs in the
On 18-Mar-15 18:59, egcastr wrote:
I need to call a C API as part of my bootstrapper to determine if a
particular feature exists on chip.
BA functions will let you do that. See the sample code in the source
code at src\burn\Samples\bafunctions.
There's no UI for it but it's a straightforward query string:
On 25-Feb-15 15:33, Phill Hogland wrote:
From time to time I come across a thread that suggests that a feature request
On 14-Feb-15 20:56, Phill Hogland wrote:
Now I can follow a TDD red to green pattern, creating a test and then adding
code to the CA/wixext until the red is resolved.
That was the goal. :) It takes a certain amount of discipline but it can
be worth it.
Thanks Bob and everyone involved!
On 09-Feb-15 14:47, Nick Ramirez wrote:
As far as a robust test, this is pretty weak. Setting a property is just a
small part of the install process. But the sum total of an installation is
to put files on the system, configure the registry, install and start
You're mixing unit
On 09-Feb-15 13:18, Phill Hogland wrote:
MSBuild project which would do the Test, and then if no failures, build the
Package, however my observation is that I can only get either the Test
'build' or the 'package' build to work.
That seems likely. MSBuild projects generally have one output so
On 27-Jan-15 04:52, dscottie wrote:
I'm trying to get Burn to install .Net 4.0.3 - if it is not already
installed - prior to kicking off my managed bootstrapper, which itself
specifically requires 4.0.3 to run properly.
You need to use WiX v3.9 to get ExePackage/@PrereqSupportPackage to
On 26-Jan-15 10:38, Phill Hogland wrote:
I want to extend the behavior of the util:User element to hide the service
account from the logon screen. If I am going at this the wrong way, what is
the correct approach?
The best approach is probably the custom attribute. In WiX v3.x,
On 19-Jan-15 10:20, Phill Hogland wrote:
This log was created while Upgrading Bundle 188.8.131.52, while Bundle 184.108.40.206
was installed (AND while Bundle 220.127.116.11 was also incorrectly listed in ARP,
as it should have been removed by the Upgrade of 18.104.22.168).
This is the log you want to focus on. It
On 18-Jan-15 15:37, Phill Hogland wrote:
I have noticed, in several different bundles and rollback situations, that if
a Bundle/@Chain contains a RollbackBoundry, and when a msi package fails
during install, right after the RollbackBoundry, that at least sometimes,
the Bundle is left in a
On 13-Jan-15 14:35, Tunney, Stephen wrote:
Rob, Bob, et al, is there any dark magic out there that can assist in this
No. DTF can read a lot and write a bit. Reassembling packages isn't on
the todo list for either DTF or Wix.dll.
On 05-Jan-15 20:58, Kevin Palmer wrote:
This works great during installation and blocks the install if the installer
is not present however when trying to uninstall the application the condition
On 02-Dec-14 16:44, Steve-Ogilvie wrote:
I have modified the theme for the boostrappers I am using
but I noticed on the Welcome screen hitting the enter key does not advance
to the next screen
is this a bug in 3.8 or as designed?
Themes don't currently expose a way to set default buttons.
On 27-Nov-14 04:37, Jože Jenkole wrote:
I have some difficulties with Wix bootstrapper. The problem is: I want to
install some prerequisites in my installation process, so in one of the exe
packages I have troubles. When this exe package is installed (with some
drivers inside) another
On 26-Nov-14 23:45, Nicolás Alvarez wrote:
I'm not sure how to handle rollback. Suppose A.msi is already
installed, I install B.msi, the update-index CA runs, and for some
reason installation fails and rolls back. The correct result is to
have the index with only pluginA.dll in it, as it was
On 31-Oct-14 18:48, Phill Hogland wrote:
The cause of the problem detailed in this thread is that I had defined a
single cab cache path without considering either $(Configuration) or
$(Platform). The fact that a different compression level was specified than
the cached cab file was ignored.
WiX v3.9 released
Friday, October 31, 2014
The production/stable release of WiX v3.9 has been released. You can
download it from here http://wixtoolset.org/releases/v3.9/stable. Read
more about the release at Rob's blog
On 11-Oct-14 12:59, Phill Hogland wrote:
This results in NIT8104: Package Failed: Fatal error during installation
Yet another bug. The Lux custom actions are written in DTF and they
aren't set up for .NET 4.0. I have a pull request ready:
On 09-Oct-14 19:15, Phill Hogland wrote:
I see that I still have the -ext WixUtilExtension on the above candle
command. I removed it but Light still fails saying that 'User' Table is
not defined. I can't find anything else in my project related to the User
table. When I first started this
On 10-Oct-14 18:01, Phill Hogland wrote:
I have a chain of Burn driven MSIs. I implemented a MSILOGGINGVALUE property
(and related variable which Burn initializes and the mba overrides). If the
MSILOGGINGVALUE property is provided to the package I do a conditional
SetProperty action on
On 10-Oct-14 18:06, sceiler wrote:
To my understanding this shouldnt happen with the use of wix binaries
checked in to TFS.
You must install WiX to be able to build inside Visual Studio. You can
build outside Visual Studio (e.g., command line or Team Build) using the
checked-in WiX binaries.
On 09-Oct-14 14:11, Phill Hogland wrote:
Since building in VS2013 with the Target Test fired after the Target
Build results in the invalid SQL error in Nit, I created a cmd batch file
to mimic the command line instructions in the chm. Lux and Candle succeed,
but Light fails with LGHT0182
On 07-Oct-14 07:29, James McConville wrote:
Thanks Bob... so there is no way to just use the default UI that doesn't
depend on .Net?
Just anxious that my uninstall is only responsible for taking things off
rather than putting them on, then off.
BAs are responsible both for UI and for
On 05-Oct-14 01:58, Nick Ramirez wrote:
I was afraid that setting RemoveOnUninstall to yes or not putting it there
at all would have the effect of removing the existing user from the system.
That doesn't happen with @CreateUser=no.
Thankfully, that does not happen. However, it also doesn't
On 03-Oct-14 06:02, James McConville wrote:
What I would like to know is, what will happen if I uninstall .Net, and then
try and uninstall my app, will I still be able to uninstall?
It will install .NET so your BA can run.
On 02-Oct-14 03:25, Orzyszek Andreas wrote:
The problem i’m faceing is that if I run the setup on a machine with .Net 4.0
Full installed the .Net 4.5.2 is not installed before my custom MBA is
That's by design. If your BA can be loaded, it is.
On 27-Sep-14 16:33, Nick Ramirez wrote:
When I run this installer, the existing user is updated so that it is now a
member of the Administrators group. However, on uninstall, the membership is
not removed from that user. Is there something else I need to add to make
On 01-Oct-14 18:43, Colin Sim wrote:
I have some questions about how best to deal with install or setup
Install defaults in per-machine locations (e.g., HKLM or ProgramData).
The first time the app runs, copy it to the running user's per-user
On 14-Aug-14 17:59, Phill Hogland wrote:
Variable=vc2013_x86_SP1 Result=state /
I recommend against using a product code search: If a user has a later
version of the runtime installed, it won't be detected. (The VC runtimes
On 09-Aug-14 15:04, James Welle wrote:
To verify my understanding, since my bundle is going to require .NET 4.5.2, I
should also make that the prereq for my MBA?
If so, I guess the disadvantage I see to this is that most users will now see
that prereq UI instead of just seeing my custom
On 08-Aug-14 17:08, James Welle wrote:
However an MBA does not inherently require .NET4. It could use any version.
That's why I think it is a bug that those variables exist in NetFx4.wxs at
all. Every bundle that uses a custom MBA should have to define those
The pre-req BA works
On 08-Aug-14 17:13, Sean Hall wrote:
The reason that the WixMbaPrereqLicenseUrl variable is missing for 4.5.1
and 4.5.2 is that there is no official direct link to the license agreement
for those versions. I'm guessing that the WixMbaPrereqPackageId hasn't
been added because both variables
On 05-Aug-14 04:36, Tobias S wrote:
Here working with Satelite MSIs or duplicating the installer logic across
several MSIs or transforming an MSI seems not the first choice...
It depends. You can still have a single source. Seems preferable to me
On 04-Aug-14 10:43, Tobias S wrote:
What are the best approaches for MSIs within multilingual bundles?
Keep neutral resources in one package, localized resources in another
package, one per language (i.e., lang pack).
On 28-Jul-14 08:51, Chetan Dabade wrote:
i scanned my whole machine but couldn't find file *Common.wxs* and in
addition under Installer.wxs file there is a variable declared as:
*WixVariable Id=WixUICostingPopupOptOut Value=1 Overridable=yes /*
while googling i found the above mentioned
On 19-Jul-14 13:09, Phill Hogland wrote:
So when this MSI is added to a bundle, I assume that Payload element should
be used with the MsiPackage element to specify the MSI and the cabinet
No need. WiX automatically harvests the external cabinets and loose
files from an MsiPackage at
On 14-Jul-14 19:34, Hoover, Jacob wrote:
I did some digging today, and if I revert my change then in the case of
Bundle A launching Bundle B for an update, it's an async update and when A
completes it tries to clean B. It may be a fringe case, but I could see
this causing issues if B
On 14-Jul-14 13:04, Wesley Manning wrote:
Interesting. Microsoft office came out with their own install technology
called Click to run. Here:
Never heard of it before. Wonder why they created that
On 6/25/2014 10:01 AM, Anton Iermolenko wrote:
Does Wix Bootstrapper extract something into the directory where Setup.exe
No but you can use Process Monitor from SysInternals to watch everything
it does. It'll pinpoint when the error occurs.
On 6/23/2014 4:50 AM, Anton Iermolenko wrote:
[14A0:0310][2014-06-21T20:02:35]w322: Skipping cross-scope dependency
registration on package: PrerequisitesMsi, bundle scope: PerUser, package
Is this intentional? You might want to make both packages per-machine.
On 6/23/2014 5:17 PM, George Fleming wrote:
1. In PatchCreation element, the Id attribute is different,
auto-generated GUID is used each time we patch.
That means you're not using WiX to build the patches but a tool like
MsiMsp. Nothing WiX can do to change the outcome. That's why pure-WiX
On 6/20/2014 1:24 PM, Kyle Corsi wrote:
light.exe : error LGHT0001 : Item has already been added. Key in dictionary:
g73E8E70EB9CA78EDD5C4CA9264E4E34F' Key being added:
Which version of WiX are you using?
On 6/15/2014 3:30 PM, Tunney, Stephen wrote:
Think I have time to squeeze this in for 3.9?
Depends on the scope of the fix. Deadline for low-bar changes was 6-June.
On 6/14/2014 3:02 AM, Rob Mensching wrote:
That sounds a lot like:
Yep. If it's not working, it could be a bug in Melt.
HPCC Systems Open Source Big Data Platform from LexisNexis
On 6/12/2014 1:15 PM, Tunney, Stephen wrote:
Can we perhaps put a compiler warning in if a bindpath isn't used?
Bind paths are a great idea but penalizing the other methods just seems
And perhaps also add a build error when a user tries to use pure wix patching
method without a
On 6/12/2014 3:40 PM, Tunney, Stephen wrote:
I had posted this question earlier but I guess it got lost in the piles of
emails going out to your adoring fans ;)
No, I'm just busy. :)
In my torch command I have -xi -xo set, and I'm still getting a cab file with
a .wixmst extension? How do I
On 6/12/2014 6:12 PM, Robert Harrison wrote:
Quick question: How to eliminate the cancel button from the UI dialog that
shows when uninstall? I am using WiXUI_FeatureTree and also referencing
WiXUI_Common. I would modify the existing dialog but my problem is that I
don't know which dialog
On 6/9/2014 5:32 PM, Ed wrote:
Wix is allowing me to create msi files with a large number in the fourth
version index (6-digit numbers, i.e. 11).
How are you authoring that? If you put such a version as a literal
string, the compiler will fail with an error message saying you can't do
On 6/9/2014 9:06 AM, Tunney, Stephen wrote:
It might be a case of The Mondays but I'm at a loss at what you are getting
at :( What are these other files that might get output by torch? How can I
supress their output?
Rename the .wixmst to .cab and open it in explorer. You'll see binaries
On 6/9/2014 6:01 PM, Carter Young wrote:
Your getting the error because the number is ignored all together,
regardless of type, int long string doesnt matter... its unable to
parse because there is no underlying code in burn that says parse 4th
Burn supports all four places of version
On 6/9/2014 6:51 PM, Ed wrote:
I understand the build version must be less than 65536, but I believe that
refers to the third index in the version number.
Product versions must be less than or equal to 255.255.65535.65535.
On 6/8/2014 5:31 PM, Phill Hogland wrote:
Is the line-feed.0 literal? If so, you broke your Product/@Version value.
On 6/8/2014 11:13 AM, Tunney, Stephen wrote:
Re: [WiX-users] Bug in torch - wixmst output is not in XML format
-xo doesn't produce a text file if there are files in the output (which
is pretty often).
On 22-Apr-14 13:58, Bruce Cran wrote:
I have two different products/bundles that install different versions of
the same msi package. I had expected that the bundle would detect the
existing installation of the msi and log it as an upgrade, but instead
it's logging it as absent and the
On 09-Apr-14 14:00, Bruce Cran wrote:
We package our MSI using Burn, and have had a request to allow users to
dump the files in one of the MSIs to a directory instead of installing
them - i.e. doing an Administrative installation
On 01-Apr-14 08:32, Pally Sandher wrote:
Anyone seen this before? I've bundles built using WiX v3.6 which are failing
to apply a patch which has been signed by a renewed code signing certificate.
The bundle was signed by the previous certificate which expired last month
but both the bundle
On 07-Mar-14 05:45, Dan Watson wrote:
1) I understand the power of Bootstrapper project in bundling multiple MSI
setups (the Office installation being a good example) but is there an
equivalent of Burn command that would package my MSI setup as setupbld.exe
did with a command switches?
On 27-Feb-14 14:45, Phill Hogland wrote:
Is there a way to display an Information message to the Output window,
without having to set the 'Verbose' property and without it being either an
Error or a Warning.
I don't think so. The info logging level doesn't really exist.
On 10-Mar-14 22:12, Dmitry Nechaev wrote:
There is no way for me to fix ICE03 error for this MSM using InsureTable for
the last dozen of tables commented out in the code above.
WiX doesn't know what those tables are so it can't create them. If the
merge modules are fundamentally broken, you
On 07-Mar-14 14:02, Joel Dart wrote:
... but I cannot figure out how to set ButtonNameState based on a different
variable or how to reevaluate such a condition.
You could use BA functions in WiX v3.8 and later but that would only let
you set the variables once, as part of planning. WixStdBA
On 08-Mar-14 17:04, Phill Hogland wrote:
I have a bundle with an mba and several nearly identical MsiPackages (which
install various printer drivers). So except for a different path to the msi
the bundle MsiPackage authoring is identical for each driver package. The
thing that I noticed is
On 11-Mar-14 16:44, Rob Mensching wrote:
NETFX 4.0 is required.
And installed by the bundle if needed.
ProjectAggregator2.msi is only necessary if you have VS2008 installed.
VS2005 only. I thoroughly enjoyed nuking that from v3.8 setup.
On 25-Feb-14 10:34, Phill Hogland wrote:
candle.exe(0,0): error CNDL0001: Stream is not a valid resource file.
Open the extension in ILSpy (etc) and make sure the name is what you're
On 26-Feb-14 18:33, Hoover, Jacob wrote:
I can reproduce a bug where releasing the Alt key doesn't clear the
accelerator key with WixStdBA.
What does clear the accelerator key mean?
On 24-Feb-14 20:41, Jun Yin wrote:
Is it possible to suppress bundle caching and registration in ARP (Add/Remove
Programs or Program and Features).
No. Burn is not a fire and forget bootstrapper. See
On 17-Feb-14 07:17, Periyasamy Chinnu wrote:
I am using Wix 3.6. I would like to create web installer using wix burn. I
saw the link for adding executable files in remote payload element and it
Like this how can i specify for msi?.
RemotePayload is just to avoid having the packages
On 19-Feb-14 12:08, Nikolay Belyh wrote:
Is there a way to use WiX in a form of a library (no executables)
Sure. All the WiX .exes are just wrappers around wix.dll.
On 15-Feb-14 18:31, Phill Hogland wrote:
In studying the source code I notice that the GamingExtension and the
IISExtension, among others, have a data\messages.xml in the wixext project
You need to run MsgGen as part of the build, like in a BeforeBuild target.
On 14-Feb-14 11:18, Hoover, Jacob wrote:
I think this is more than just resigning
Unless you were doing the particular thing they're now ruling out, you
shouldn't have to re-sign anything.
Will this impact Wix and Burn as a similar technique was used to put the BA,
On 11-Feb-14 10:22, Tony wrote:
Bob do you want me to file a bug, or has this been done already?
Please file a new one. There was a bug on ComPlus but not the others.
On 11-Feb-14 14:56, Hoover, Jacob wrote:
To answer my own question, don't use an outdated MSI with a newer CAB file
(though I am still not certain why it caused the issue). I was under the
impression that if the CAB was signed there was no additional verification
done on the CAB. If in
On 11-Feb-14 19:33, Phill Hogland wrote:
In one test scenario it works as expected, but in another scenario the
'text' 'string' which is passed to one of the columns results in the value
being treated as an 'identifier', which I do not understand.
How are you setting the fields?
On 11-Feb-14 10:11, Hoover, Jacob wrote:
I've been signing and deploying for several years now, but with the latest
release I've ran into a strange problem. The first error complains about a
difference in size between the certificate in the CAB verses what's in the
package. The second
On 11-Feb-14 05:22, Holpp, Stefan wrote:
MSBUILD : PKG error : ID E6125: *** : File version for Assembly
'C:\dir1\dir2\someExample.dll' (feature 'EXAMPLE') not found. ...
That's not a WiX error message.
On 04-Feb-14 07:40, Tony wrote:
votive install contains wixcomplusextension.dll and wixmsmqextension.dll
wix38-binaries contains retina.exe (and config)
That would be a bug. I think Complus was added for v3.9.
On 04-Feb-14 17:42, Martin Alley wrote:
I found the instructions in using this extension in a sample WiX setup
project a little confusing. I don’t get why the reference should be added as
a project reference
It shouldn't. There's nothing to hook up .csproj references as WiX
On 31-Jan-14 11:42, Phill Hogland wrote:
I am probably over looking something simple, but in a Wix Custom Table Row
element, how do I indicate that I want the data in that row (to be passed
to a CA) to be a component's attributes?
Not sure what you mean. Attributes are usually represented as
On 29-Jan-14 14:59, Barnes, Karen wrote:
I would really like to see an example of how the list view works with the a
custom theme file in the bootstrapper project. It appears to allow me to
enter in the item within my VS2012 Bootstrapper project, but once I added it,
On 28-Jan-14 10:52, Daniel Madill wrote:
However, in my original MSI I set the ARPINSTALLLOCATION property so that the
install location shows up in ARP. I would like to do the same thing with my
new burn-based installer. However, burn creates its own ARP entry for the
bootstrapper. How do I
On 19-Dec-13 12:16, Wheeler, Blaine (DSHS/DCS) wrote:
I expect to see the bundle install the upgraded msi and to leave the
unchanged package in place. But Burn installs the upgrade and then removes
the unchanged package even through the InstallCondition for package #2
On 16-Dec-13 08:44, Graham Harwood wrote:
My question is, what reason does the CA for the firewall not update an
application rule if one already exists?
The quarter came up tails. :) That was the behavior I needed when I
designed the firewall extension. Both behaviors are right. It'd be
On 12-Dec-13 13:40, Brian Enderle wrote:
I have the following ICE errors and am not sure how to track down the root
cause or how to repair. Can someone explain how I can find the cause of
these errors and fix them?
I am trying to use the Crystal Reports 13.0.7 MSM file to deploy CR with my
On 12-Dec-13 14:52, Tunney, Stephen wrote:
Can melt simply rebase the wixpdb if I were to point it to an already
existing melt output directory? I basically don't want to have melt
re-output everything to the -x argument again. Nothing on the help syntax
for 3.7 indicates a way of doing
The final build number is 3.8.1128.0.
On 28-Nov-13 11:48, Nicolás Alvarez wrote:
2013/11/28 Rob Mensching r...@robmensching.com:
WiX v3.8 released: http://wixtoolset.org/releases/v3.8/stable
Read more about it here:
On 08-Nov-13 09:23, John Cooper wrote:
I know that part of the issue is that some of the ICE stuff (supplied by
Microsoft) still depends on VBS. The other part is that CIS departments are
loath to give rights to run the Windows Installer Service to
On 09-Nov-13 19:36, Suryadeep Biswal wrote:
I am getting an System.InvalidOperationException while compiling
a WXS file with util:PermissionEx
element under RegistryKey element. I
am using WIX build 3.6.3303.0.
Known bug that was fixed in WiX v3.7.
On 07-Nov-13 11:33, Simon Gustavsson wrote:
I'll just have to live with that warning. However, to me, it looks like the
version warnings are just an oversight. Is that so?
Burn writes the DisplayVersion value instead.
On 10-Nov-13 17:12, Blair Murri wrote:
Bob, I would love to find where the setting is to allow non-admin service
accounts to perform per-user windows installer operations. I've searched for
it without success. I'm sure I could get some administrators to loosen that
particular restriction on
On 01-Nov-13 11:26, Christopher Painter wrote:
So that made me wonder, has this part of WiX been updated for VS2013 in WiX
Nope. Please file a bug.
Android is increasing in
Android is increasing in popularity, but the open development platform that
developers love is also attractive to
On 28-Oct-13 11:21, Tunney, Stephen wrote:
Now I am getting an error in melt.exe. Looks like a path issue or WiX DLLs
not being added to the GAC for some reason. Copying files from the SDK
folder to the bin folder have resolved this issue but this is likely a bug in
On 28-Oct-13 04:43, Selva wrote:
*1. To show the Splashscreen i have applied *DelayStart* for 5sec but its
There's no variable used for that purpose.
2. During UnInstall, the VBagent.msi is not getting uninstalled when we
uninstall the Master Package.
Check the Burn log to see
On 28-Oct-13 20:38, Tunney, Stephen wrote:
Adding DirectoryRef to the same boat as FeatureRef. I've added all
directoryRefs, including the one that includes the component that I know has
been updated and still no dice. :(
When used in patch family filtering, only a ComponentRef will include
Thanks for everything so far! WiX rocks!! :)
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: October-28-13 9:37 PM
Subject: Re: [WiX-users] Purely WiX patching and FeatureRef
On 28-Oct-13 20:38, Tunney, Stephen wrote
There was a separate bug for templates: http://wixtoolset.org/issues/4093/
That's now fixed and available in WiX v3.8.1021.0.
On 21-Oct-13 13:39, Hoover, Jacob wrote:
* Merge branch 'bugs_3839_4093.2' of
On 16-Oct-13 09:20, Michael Stoll wrote:
Is it possible to access the InstallCondition attribute from a MBA, when
the launch action is modify?
No, that's not exposed to the BA. Please file a feature request. It can
be additional detail added to the BA manifest.
1 - 100 of 4214 matches
Mail list logo