I've got an installer package which installs my product. I need some additional drivers installed, so I've added a folder which contains a 64-bit and 32-bit EXE (two separate files). Along with these EXE's are some other files that the driver installer requires -- a dll, some ini files, etc.
I've then added a custom action that attempts to silently install both files - the 32-bit version runs first followed by the 64-bit. I did this because I didn't know how to make it run the appropriate version; it works out because the 32-bit version will fail silently on a 64-bit system and vice versa. The drivers install great.
The problem comes when I install a new version of my application. I'll go to the "Product Details" inside of Advanced Installer and specify a new version then answer with "Major Upgrade" when prompted. If I then install that new version over the top of the other, I get a message saying "The file 'CP210_x64.exe' is not marked for installation." and the installer aborts.
Here's what else I know:
- If I immediately install again, I do not get the message.
- If I uninstall the old version manually, then install the new version, I do not get the message.
- The only time I get the message is if I install a new version on top of an old version.
Any tips?
FOLLOW US
Get the latest news in Application Packaging