Install prerequisites first
Use Bundle when the product needs runtimes or other EXE/MSI packages before the main application package.
InstallerLab v3 keeps Bundle as a normal FSS build target. For Application projects it can chain prerequisite EXE/MSI packages before the main MSI. For Office Add-in and QGIS Plugin projects, Bundle wraps the same specialized MSI backend instead of reimplementing activation or lifecycle behavior in Burn.
Use Bundle when the product needs runtimes or other EXE/MSI packages before the main application package.
The FSS remains the project. There is no second product definition just for Burn.
Bundle calls the MSI backend, receives the generated main package and then builds the Burn chain around it.
Office registration and QGIS plugin lifecycle remain in their MSI implementation; Bundle does not duplicate those commands.
The final Bundle is a single executable bootstrapper even when the installation contains multiple packages.
InstallerLab uses WixStandardBootstrapperApplication with project-aware icon/logo/theme resources and the shared language resolution policy.
| Need | Pure MSI | Bundle EXE |
|---|---|---|
| Main Windows Installer package | Yes | Included as main package |
| Chain prerequisite EXE/MSI packages | No | Yes |
| Single bootstrapper EXE | No | Yes |
| Use the same InstallerLab FSS | Yes | Yes |
| Office/QGIS specialized lifecycle | Handled by specialized MSI | Reuses that MSI |
| WiX required on build machine | Yes | Yes |
InstallerLab can run without WiX. Creating MSI or Bundle requires the WiX 7.x CLI; Bundle requires BootstrapperApplications and uses Util when prerequisite detection needs it.
dotnet --info
wix --version
wix extension list -gYes. The Bundle backend generates or reuses the main MSI flow and builds the final bootstrapper through WiX Burn.
Yes. The current prerequisite chain supports local EXE/MSI packages where that project workflow applies.
Yes. In v3 Bundle wraps their specialized MSI backend rather than duplicating Office/QGIS logic.
No. The same editable FSS remains the source of truth.
InstallerLab v3 keeps Burn as a wrapper around the package logic already owned by the MSI backend.