burn

问题 I created a WIX Burn setup. The Bundle chained multiple .MSI files for global installation (all MSI support downgrading). <Bundle Name="APP 4.3.0" Version="4.3.0" Manufacturer="Manu" UpgradeCode="$(var.UpgradeCode)"> <Chain> <PackageGroupRef Id="VCppRedistPackage"/> <PackageGroupRef Id="DotNet4Package"/> <MsiPackage Id="CrystalReportPackage" SourceFile="$(var.SolutionDir)_CommonFiles\CRRuntime_32bit_13_0_9.msi" DownloadUrl="http://MyAppRuntime/CrystalReport_NET40/CRRuntime_32bit_13_0_9.msi"

问题 I am very new to the installer world. I have successfully made an .msi for my application and it is building with short-cuts and also uninstalls correctly. My next goal is to package .Net 4.5 with the installer and have it be installed prior to the installation of my application. I also have a third party application that needs to be installed. It is packaged as an msi. From what I can gather I need to develop a Bootstraper solution to have these applications install in sequence. Can anyone

问题 I'm working on a application, which works on top of WiX bundle, and communicates via embedded pipe (by utilizing ManagedBundleRunner) and receives progress and error updates. Currently I use the standard WiX bootstrapper. However, I will be creating custom managed bootstrapper to implement custom behavior. Part of this new behavior is a bidirectional communication of my application with the bootstrapper. After exploring WiX source (especially Burn engine), I've come up with two approaches: 1)

问题 I am trying to create an ExePackage [using the DownloadUrl property] in my bundle that downloads Sql Express 2014 and installs it using the following code <ExePackage Id="Sql2014Express" DisplayName="SQL Server 2014 Express" Cache="no" Compressed="no" PerMachine="yes" Permanent="no" Vital="yes" Name="SQLEXPRWT_x64_ENU.exe" DownloadUrl="http://download.microsoft.com/download/E/A/E/EAE6F7FC-767A-4038-A954-49B8B05D04EB/ExpressAndTools%2064BIT/SQLEXPRWT_x64_ENU.exe" InstallCommand="/ACTION

问题 I am trying to create a custom UI for WiX and Burn. I'm almost done except one thing. In the end of installation which is upgrading(for exaple 1.0.0 to 1.1.0) uninstall for the previous version starts and the UI of it shows. My question is how should I handle this so the user doesn't see uninstall UI in the end. 回答1: When performing an upgrade of a Burn-based installer, the process will upgrade each of the MSIs bundled inside the installer, then it will uninstall the previous version's bundle

问题 in a wix burn bootstrapper bundle : how to detect whether ms vcredist 2013 x86 is present or not? i'm doing a check for the Upgrade Id / UpgradeCode of that particular package, but the bundle always installs it afresh, even though it is installed already. ... <Bundle> ... <Chain> <!-- redist packages --> <PackageGroupRef Id="redist"/> ... </Chain> </Bundle> <Fragment> <PackageGroup Id="redist"> <PackageGroupRef Id="redist_vc120" /> ... </PackageGroup> </Fragment> <Fragment> <!-- vcredist 2013

问题 I'm looking at using Burn as a bootstrapper for an installer and I need to pass in a couple of arguments into the MSI. I know that the way to do this is to use MsiProperty elements, the issue I am having is with displaying the UI to capture those properties. I'm aware that I can create a completely custom UI via the managed bootstrapper application host, however this is turning out to be a lot of work to implement for a relatively minor tweak to the bootstrapper. I've found this blog article

问题 I am making a package installer and am followin the KISS principle. No bundle made in WiX 3.6-3.8 works on Windows XP (but works as expected in Windows 7). The cause is elevation error 0x800705b4. [14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to wait for child to connect to pipe. [14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to connect to elevated child process. [14DC:15A8][2014-02-12T11:54:46]e000: Error 0x800705b4: Failed to actually elevate. [14DC:15A8]

问题 There are 3 bundles, code is listed below. 1.0.0, 1.0.0.1, and 2.0.0. If 1.0.0, 1.0.0.1, and 2.0.0 are installed, View Installed Updates will still have 1.0.0.1 listed as installed. It will remain there until the last Version is uninstalled. <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Bundle Name="Burn Installer" Version="1.0.0" Manufacturer="LANSA" UpgradeCode="AAAAAAAA-AAAA-AAAA-AAAA-AAAAAAAAAAAA" Copyright="..." AboutUrl="..."> <BootstrapperApplicationRef Id=

问题 I already posted a related problem here: Wix: Managed BA command line not effective, which is about command line passed during upgrade. Now I tried to explore, how it interpret the command line. Here is my run method to do so: protected override void Run() { string cmdOptions = string.Empty; this.Engine.Log(LogLevel.Verbose, "Launching custom TestBA UX"); Debug.WriteLine("Command.Display: {0} Command.Action: {1}", this.Command.Display.ToString(), this.Command.Action.ToString()); Environment