Purpose: Comprehensive list of different Installer Engines and a way to install each of them silently.
Every single task of “let us install this application without user interaction” begins with the study of the target application. You might be lucky to find out that the application is created by one of the most popular install engines. If so, you have a chance to use the applicable install engine documentation and parameters to automate the installation. If not, you will need to create an install package by yourself.
How do you know, which Install Engine does your current project use?
1. After a while, you will notice the engine from how the Installer works.
2. Before that, you can use the following methods to detect the engine. With these methods, you might be able to get the silent installation switch directly, but for further customization of the installation package you will need to know the engine.
|I.||Launch the following application to determine the most obvious of engines|
|II.||Launch your installation setup executable file from the command prompt with the following parameter to determine any documented basic inbuilt parameters||/?
|III.||You are out of luck! Start going through one of the following actions
a. You might have a custom extractable setup, try to extract it more to get in touch with the actual install files.
b. The Setup is extracting the actual installation files somewhere in your current system (%temp%, %appdata%/temp, etc.) find them.
c. You have an unknown installation engine or custom built installation engine, you need to PACKAGE it yourself.
|1.||Windows Installer (MSI)|
|2.||Windows Installer Update (MSP)|
|3.||Inno Setup (Script Based)|
|4.||Install Shield (EXE)|
|5.||Install Shield Legacy (EXE)|
|6.||NullSoft Installer (NSIS)|
|7.||Win32 Cabinet Self-Extractor|
|8.||Setup Bootstrap for Visual Basic Setup Toolkit|
|9.||Wise Setup Installer|