Application MSI
Reuse metadata, files, destination, registry, shortcuts, directory permissions and supported service rules from the same FSS.
Build a real MSI from the same FSS project — including specialized Office and QGIS projects.
InstallerLab v3 keeps the normal Application MSI workflow and extends the backend with dedicated Office Add-in and QGIS Plugin semantics. The project stays visual/FSS while WiX authoring is generated by the backend.
MSIWiX 7 backendApplicationOffice Add-inQGIS PluginmsiexecEmbedded CAB
One MSI backend, project-aware behavior
Office Add-in MSI
Deploy supported Excel, Word and PowerPoint VBA add-ins with specialized installation/activation lifecycle instead of pretending they are normal EXE applications.
QGIS Plugin MSI
Deploy a folder/ZIP plugin to the correct current-user QGIS profile using stable PluginId-based identity.
Windows Installer output
The resulting package is a real MSI suitable for msiexec and managed deployment where the project semantics allow it.
Embedded cabinet media
Application payload media can be embedded so the expected output is the MSI rather than a loose external CAB.
Smart build targets
Office Add-in and QGIS Plugin FSS projects automatically disable EXE/Portable targets and leave MSI and Bundle available.
Pure MSI or Bundle?
| Need | Choose |
|---|---|
| Main Windows Installer package only | MSI |
| Prerequisite EXE/MSI packages before the product | WiX Burn Bundle |
| Single bootstrapper EXE containing the chain | Bundle |
| Direct msiexec deployment | MSI |
| Office/QGIS plus Bundle UX | Bundle wrapping the same specialized MSI |
Bundle does not duplicate Office or QGIS lifecycle logic. It builds and consumes the same specialized MSI backend.
Useful MSI commands
Silent install
msiexec /i "MyApplication.msi" /qn /norestart /L*v "install.log"Silent uninstall
msiexec /x "MyApplication.msi" /qn /norestart /L*v "uninstall.log"WiX 7 requirement
InstallerLab itself can run without WiX. Creating MSI requires the WiX 7.x CLI on the build machine. Bundle additionally uses WixToolset.BootstrapperApplications.wixext and uses WixToolset.Util.wixext when prerequisite detection requires it.
MSI builder FAQ
Does InstallerLab create a real MSI?
Yes. The MSI backend builds Windows Installer packages through WiX.
Do I need to write WiX XML?
Not for normal InstallerLab authoring. The project is defined visually/FSS and translated by the backend.
Can Office Add-ins and QGIS Plugins use MSI?
Yes. In v3 they are explicit specialized project types and MSI is their primary installer target.
Can I import an Inno Setup project and then create MSI?
Yes when the converted FSS is compatible with the MSI backend; review it with FSS Analyzer first.
Use MSI when Windows Installer is the destination, not the authoring experience.
Keep the project in FSS and let InstallerLab select the correct MSI behavior for its ProjectType.