I was wondering if you have a guide on the best methods for creating updates for simple applications (application with one feature).
I've tried the one patch per update, but the QA found this method not satisfactory, because the updater presents multiple updates with check boxes by each update. This was found to be confusing. Some users, if upgrading two version at a time, uncheck the middle version causing them to not be able to update at all.
Example: User is on 1.1.3
[*] 1.1.5
[ ] 1.1.4 <- user unchecks this option in the updater application.
The update fails to work because 1.1.5 was created to move from 1.1.4 -> 1.1.5.
So I've started to create patches with multiple targets and one upgraded version. So the 1.1.5 patch project would have 1.1.4, 1.1.3, 1.1.2, etc. as the targets.
This worked fine until the patches started becoming very large due to the amount of targets, let's say 7 targets. The more targets caused more of the typical window installer problems to arise, like 'Unable to find *.tmp', the patch randomly freezing when copying files, and complains of missing the *.msi file.
It looks like patch sequencing might be a solution, but I never seem to have enough time to plow through the Windows Installer Documentation on msdn.com to figure out if it is a solution, and my attempts to blindly create a patch project with patch sequencing in AI have led to nothing.
I've looked through past forum posts, but have been unsuccesful in finding a good response. A response, a link to an old forum post, or an external link that answer these questions would be most appreciated.
FOLLOW US
Get the latest news in Application Packaging