I've an EXE app (contains few thousand files) packaged with AI v15.3. Already released multiple versions of this app. So far everything is working fine. Each version have different Product Code and using the same Upgrade Code. The packaging was set to uninstall the old version first before installing the new version.
Some users complain that they have to download the full version in order to update to the latest version of my app. FYI, until now, the different between each app version is minor: different version of dll, exe etc... I tried to create a patch between those app versions but so far none worked.
Scenario 1:
MyApp v1.1.0 -> Original version
MyApp v1.2.0 -> update some dll files, different Product Code
During patch building, it will show major patch detected but still managed to create the patch file. Running the patch file with the v1.1.0 installed will prompt the message of missing the program to be upgraded (although v1.1.0 did exist).
Since my app are currently based on Scenario 1, I was wondering whether it is possible to create a small installer (maybe an EXE) that contains whatever updated files. What I'm trying to archive is:Scenario 2:
MyApp v1.1.0 -> Original version
MyApp v1.2.0 -> update some dll files, same Product Code as v1.1.0
What I did is just duplicate the original project file and rename it to MyApp_v120 and then update it to version 1.2.0. When I create a patch from both msi (extracted from the EXE), during building it will produce warning of component ID changed and sequence changed. I open the msp file with Orca but it doesn't contain the updated files.
Is it possible to do this Preferred Scenario?Preferred Scenario:
MyApp v1.1.0 -> example Product Code: 10001, Upgrade Code: 70001
MyApp v1.2.0 -> example Product Code: 10432, Upgrade Code: 70001
MyApp v1.3.0 -> example Product Code: 12982, Upgrade Code: 70001
This custom EXE, should be able to update the previous version installation with new updated files AND also update the Product Code with the one used by the full installer. For example: v1.1.0 updated to v1.2.0 and change the Product Code to 10432.
I'm hoping the above scenario doesn't affect the standard Updater function (using the Advanced Updater) where the user should still be able to get an update reminder when it's available.