I tested my patch by applying it manually to a cached web media installation. As it was described in the whitepaper, I had to specify the cached directory. After that, the patch was sucessfully applied, and the application was updated.
When I deploy the exact same patch to a similar installation, The update manager downloads it, and it appears to apply the patch, but the installation goes way too fast, and afterwards the old version of the programs remains.
On this target computer I cannot find any artefacts of the patch. The only inidication that it dealt with it, is that it is not downloaded again when re-checking for updates.
What could go wrong here?
Could it be a problem that the product name changed between the two versions? The product code is still the same though.
Patch work when applied manually, but not through web update
further investigation
Investigating further I found out that the new version number is noted in the file
C:\\Dokumente und Einstellungen\\All Users\\Anwendungsdaten\\{C9E4B347-FD79-4732-9B5A-4AB217CCBA20}\\installedupdates.dat
and in different subfolders of C:\\Dokumente und Einstellungen\\All Users\\Anwendungsdaten\\{C9E4B347-FD79-4732-9B5A-4AB217CCBA20}\\offline\\ I can find the old and the new version of the main application executable file.
C:\\Dokumente und Einstellungen\\All Users\\Anwendungsdaten\\{C9E4B347-FD79-4732-9B5A-4AB217CCBA20}\\installedupdates.dat
and in different subfolders of C:\\Dokumente und Einstellungen\\All Users\\Anwendungsdaten\\{C9E4B347-FD79-4732-9B5A-4AB217CCBA20}\\offline\\ I can find the old and the new version of the main application executable file.
solved
The problem was that I canged the product name, not the product code though.
I had to create a full installer that performs an update.
I had to create a full installer that performs an update.