burn

I have a setup MSI for our application, and I also have signed FTDI drivers that need to be installed as well. I'd like for them to be installed with Burn rather than the WiX MSI to keep CustomActions out of the MSI (however, I've tried the CA route as well). I've tried putting the instruction in an ExePackage , but the SourceFile attribute asks for the file location during build, not runtime (e.g. <ExePackage Id="InstallDrivers" DisplayName="Installing Drivers" SourceFile="[InstallFolder]Drivers\DPInst.exe" InstallCommand="/SA /SW" PerMachine="yes" After="MyMSISetup" Description="Installing

Using very simple code almost same as in examples: <?xml version="1.0" encoding="utf-8"?> <Wix xmlns="http://schemas.microsoft.com/wix/2006/wi"> <Bundle Version="1.0" Manufacturer="ACME" UpgradeCode="6AF8AF7D-3B44-4496-9E64-56206DF66C55"> <BootstrapperApplicationRef Id="WixStandardBootstrapperApplication.RtfLicense"/> <Chain> <MsiPackage SourceFile="wpftoolkit.msi"/> </Chain> </Bundle> </Wix> I get a setup.msi file that produced error imidiatly in start: msiexec /i setup.msi /l*v log.txt log.txt: === Verbose logging started: 02.10.2013 14:12:11 Build type: SHIP UNICODE 5.00.7600.00 Calling

I have written a managed wix bootstrapper using WPF. The actual installation steps requires chaining of multiple msi's/exe's and batch files. <Chain> <MsiPackage SourceFile="xxx"/> <ExePackage Id="Test" SourceFile="..\TestBatch.bat" Vital="yes"/> <MsiPackage SourceFile="yyy"/> </Chain> During the execution of each package, a message should be displayed (preferably from the bootstrapper UI) indicating which msi/exe package/ batch file is being executed currently. In short, a ProgressText is needed in the bootstrapper How can I make this happen? Another question: I do not want all the msi's to

I am new to Wix burn bootstrapper so pardon my ignorance.I have a requirement where i need to install a pre-requisite using burn bootstrapper. The prerequisite is a setup.exe(third-party) which has dependency on files and a folder(containing couple of files).All these need to exists in the root of setup.exe for the setup.exe to run successfully. example structure-- setup.exe samplefile.rsp files(this is a folder which contains files needed by setup.exe) Data1.cab Clientruntime.msi anotherfile Here is what i got so far. <ExePackage Id="Ingres_Client" Compressed="yes" PerMachine="yes" Permanent=

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 x86 --> <?define vcredist2013minversion="12.0.21005"?> <Upgrade Id="B59F5BF1-67C8-3802-8E59

I have a WiX Burn custom installer using ManagedBootstrapperApplicationHost. After installing one of the prerequisite Microsoft Windows Installer 4.5 I forcefully reboot the PC (Windows XP) using: <ExitCode Behavior="forceReboot"/> The Bundle chain looks like this: <Chain> <PackageGroupRef Id="WindowsInstaller45"/> <PackageGroupRef Id="Netfx2Full"/> <PackageGroupRef Id="Netfx4Full"/> <PackageGroupRef Id="CustomPkg"/> <PackageGroupRef Id="SQLExpress"/> </Chain> After it reboots, I want my installation to continue after that, but it actually detects the installation and shows Uninstall option.

I'm using WiX 3.7's Burn/Managed Bootstrapper Application features to create a custom MBA-based installer. For each of the packages in my bundle's chain, when performing a MinorUpdate, I can easily detect which of the package features are already installed to ensure I maintain those feature selections during the upgrade by using these events provided in the WiX base class for the bootstrapper: DetectPackageComplete , DetectMsiFeature , DetectRelatedBundle , DetectRelatedMsiPackage , DetectComplete . However, during a MajorUpgrade, I'm only seeing a way to determine which package(s) are