InnoSetup Script Joiner: Combine Multiple Installers Easily is a conceptual or third-party workflow approach used by developers to merge separate Inno Setup installations into a single, cohesive master installer. Rather than forcing a user to manually run multiple .exe setup files (such as a main app, a database engine, and a required runtime), this methodology bundles them into a single wizard interface.
While it often refers to custom build automation scripts, the underlying functionality relies heavily on built-in Inno Setup features like the Inno Setup Preprocessor (ISPP), the [Files] section, and the [Run] section. Key Capabilities & Mechanics
Bundle Sub-Installers: You can embed external .exe or .msi installers inside your main installer’s data package.
Silent Installations: It passes command-line parameters (like /VERYSILENT, /SUPPRESSMSGBOXES, or /NORESTART) to secondary installers so they run completely in the background without interrupting the user.
Conditional Execution: Developers use the [Components] or [Tasks] sections to let users choose exactly which sub-programs or dependencies they want to install via checkboxes.
Temporary Extraction: Bundled installers can be automatically unpacked to a temporary folder ({tmp}), executed in sequence, and deleted immediately afterward to save disk space. How to Merge Installers (The Manual Method)
If you do not have a dedicated third-party “Joiner” GUI tool, you can achieve the exact same result natively within a standard .iss script using this standard structure:
[Setup] AppName=Master Suite Installer AppVersion=1.0 DefaultDirName={autopf}\MasterSuite [Components] Name: “main”; Description: “Main Application”; Types: full compact custom; Flags: fixed Name: “runtime”; Description: “Install Required Runtime Dependency Component”; Types: full [Files] ; Extract the sub-installer to the temporary directory during setup Source: “C:\PathTo\DependencySetup.exe”; DestDir: “{tmp}”; Flags: deleteafterinstall; Components: runtime [Run] ; Run the sub-installer silently if the component was selected Filename: “{tmp}\DependencySetup.exe”; Parameters: “/VERYSILENT /NORESTART”; Flags: waituntilterminated; Components: runtime Use code with caution. Common Use Cases
Prerequisite Bundling: Automatically installing software dependencies like the Microsoft .NET Desktop Runtime, Visual C++ Redistributables, or DirectX alongside a video game.
Software Suites: Combining several independent tools created by the same developer into a single “all-in-one” utility package.
Driver Packages: Forcing hardware-specific driver installers to run silently immediately after installing a device configuration control panel. Alternative Approaches
If you want an easier visual environment to manage multi-file setups, tools like Inno Script Studio provide an intuitive graphical interface that reduces the need to write raw code by hand. For compiling completely separate scripts altogether, creating a simple Windows batch file (.bat) utilizing the Inno Setup command-line compiler (iscc.exe) is standard practice.
Are you trying to combine specific software dependencies (like .NET or SQL Express) into your installer, or are you looking to merge two entirely separate applications? Inno Setup – JRSoftware.org
Leave a Reply