bootstrapper

问题 I have created a wix bootstrapper that runs fine on all computers when no theme file is used. If I use a theme file, it will run on my computer but not on anyone else's. <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" > <bal:WixStandardBootstrapperApplication LicenseFile="C:\eula.rtf" ThemeFile="C:\myTheme.xml" /> </BootstrapperApplicationRef> 回答1: First, look at the bundle log file on the other machines to see the error. Likely the message will indicate there

问题 Looking through the source of the Wix Standard Bootstrapper application, it appears that each package has a DisplayName property: pPackage->sczDisplayName However, the BootstrapperCore dll that is used in the WiX Setup project does not have this property. Is there any way to extract this property from the bundles in managed code? 回答1: I ported the Bal code into C#, trying to make it work exactly like the C++ code: using System; using System.Collections.Generic; using System.IO; using System

问题 Looking through the source of the Wix Standard Bootstrapper application, it appears that each package has a DisplayName property: pPackage->sczDisplayName However, the BootstrapperCore dll that is used in the WiX Setup project does not have this property. Is there any way to extract this property from the bundles in managed code? 回答1: I ported the Bal code into C#, trying to make it work exactly like the C++ code: using System; using System.Collections.Generic; using System.IO; using System

问题 I have a Bundle that installs and uninstalls VC 2012 redist. Its working fine if there was no VC 2012 redist installed previously. if there is a VC 2012 redist already installed, then while uninstalling my bundle, it uninstalls the VC 2012 redist as well. All I want is that it must not uninstall the VC 2012 redist if it was previously installed. I was trying to use the variable element with persisted attribute set to "yes". But I am not sure how it works. any pointers to this is greatly

问题 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)

问题 Wix 3.6. I'm trying to run a bundle : <Bundle Name="Setup" Version="1.0.0.0" Manufacturer="Bentley" UpgradeCode="37d68094-0b98-4b16-bfbe-7f0d3015064a"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense" /> <Chain> <MsiPackage SourceFile="path/to/MyMsiFileWhichIsFine.msi" Cache="yes" Compressed="no" InstallCondition="1"/> </Chain> Result from execution : 0x800b0109 A certification chain processed, but terminated in a root certificate which is not trusted by the

问题 I've been looking to make my bootstrapper work with installing .NET 4.0 and my own application. I reviewed several blogs and tutorials, but I can't get it to work. I read in Stack Overflow question Initiate / call bootstrapper in WiX that you need to invoke both in the bootstrapper. My bootstrapper only invokes the .NET 4.0 installer. This is the part that should invoke both parts: <Chain> <PackageGroupRef Id="NetFx40Redist" /> <MsiPackage SourceFile="C:\my app.msi" Cache="yes" Visible="no"

问题 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

问题 I'm trying to use msbuild GenerateBootstrapper task to distribute a .net application with the framework, without the need of internet connection to install it. I've found many posts that all lead to the same instructions in here: Enable Samesite for the .NET Framework 3.5 SP1 bootstrapper After following the instructions, I still cannot generate the bootstrapper. The more obvious issue I can see is that extracting the files from dotNetFx35.exe does not extract the same list of files and