
Because this project has dependencies on several third party drivers, I wanted to build a simple install script using the relatively new (as of this writing) Burn bootstrapper. So for single file OEM graphical installers, the Wix Burn tutorials worked great.
But the one thing I did not see shown was the proper use of the payload tag to tell Burn about a dependency that a chain element needed in order to execute. Yes, if you understand it, it is obvious but when I was figuring it out, it was not so obvious.
Let’s say you want Burn to execute “foo_setup.exe” but it depends on “foo_config.ini”. You want both files embedded in your final installer and it is a critical install that must succeed:
<ExePackage Id="foosetup" vital="yes" Compressed="yes" SourceFile="pathtofoo_setup.exe"> <Payload Id="fooconfig" Compressed="yes" SourceFile="pathtofoo_config.ini" /> </ExePackage >
Hope that helps somebody just getting started with Burn and multi-file chain elements. You can add as many payload elements as you like to embed each file in your installer.
3 Responses
So payload basically group files into a single package. Is there any other usage for this? Can you please tell me fully about this.
Thanks,
Can you execute an ExePackage only when uninstalling (ignore on install) the bundle?
Hello I want to install SQL server 2016 as part of my bootstrapper . so i cannot compress it inside bootstrapper as the size exceeds 2 GB , is there any other way to do it ? like keeping the source files in the same directory as my bootstrapper during installation and invoking the sql exe.
I cannot use the payload element as there are thousand of files 🙁