Hi,
Basically, this could be done by using prerequisites. You can read more about prerequisites here:
http://www.advancedinstaller.com/user-g ... requisites
http://www.advancedinstaller.com/user-g ... tware.html
However, this solution is normally used like this:
- the first "setup.exe" which installs the drivers is added as a prerequisite to your Advanced Installer project
- your Advanced Installer project installs your application
Therefore, the easiest way for what you need to do is to recreate the installation package of your application by using Advanced Instaler and add the "setup.exe" file with the drivers as a prerequisite.
If you need to use both "setup.exe" files and you don't want to use the Advanced Installer features in your installation, then you can take this approach:
- create a new Advanced Installer project
- add the "setup.exe" which installs the drivers as a prerequisite
- add the "setup.exe" which installs your application in the "Files and Folders" page
- go to the "Custom Actions" page and create a "New Installed Custom Action" under the "InstallExecuteSequence" -> "InstallFinalize" standard action (in order to see "InstallFinalize" you can use the "Show standard action" button on the toolbar)
- when prompted for the file used by the custom action select the "setup.exe" you added in the "Files and Folders" page
- use these settings in the "Custom Action Properties" page:
Code: Select all
Execution Properties: Asynchronous execution, do not wait for return
Expression: (NOT Installed)
If your installation has an User Interface, then you can make the installation package created with Advanced Installer silent. This can be done by using the "Limit to basic user interface (simple progress and error handling" option in the "Install Parameters" page.
Note that if you use Advanced Installer to create the installation package of your application, the uninstall is handled automatically by Windows Installer. Therefore, the uninstall process for this approach must be configured manually.
If the "setup.exe" file which installs your application is MSI-based, then you can use a custom action which launches msiexec.exe with a command line which uninstalls your application. If it's not MSI-based, then you need a custom action which launches the uninstall of your application.
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging