I recently switched from InstallShield to Advanced Installer Professional and am trying to distribute a major upgrade to my customers. Unfortunately the way they currently receive the update is through an in-app custom update method that download the new installation and runs a command line upgrade. I used to always distribute upgrades as a SingeImage (executable) that is then executed after download with the command line argument "/s /v/qb+", e.g. "setup.exe /s /v/qb+".
My problem is that when I distribute the "Single EXE setup" generated with Advanced Installer, my current installations will attempt to run the setup using above-mentioned command line argument. The command line fails with an error message "Invalid command line". The same thing of course happens if I manually run the same command in a command prompt. This is of course because the command line arguments "/s" and "/v" are proprietary arguments for the InstallShield EXE bootstrapper.
My question therefore is whether it is possible to create an installation that will ignore any command line arguments specified?
After all my problem is that I cannot remove/modify above-mentioned command line argument until the customers install the new upgrade (where the command line is no longer hard-coded). I also can't distribute an msi upgrade or similar, since the upgrade method expects an executable file with a specific file name.
Perhaps my only choice is to create a wrapper around the setup.exe file, but I would prefer if there is better/easier solution.
Any suggestions or alternate solutions are greatly appriciated.
FOLLOW US
Get the latest news in Application Packaging