Hi Liviu, thanks for the feedback.
I checked all the points you went through by e-mail and performed several tests. All rules described in the documentation are being followed, including the GUIDs you mentioned.
I still haven't figured out the real reason for this failure with the demonstrated versions, but talking to the team we believe that using the "Patches to Replace" feature can be a viable alternative to get around this problem since this way we only have a visible patch for the user with the last version applied, and also because we guarantee that the user will uninstall the patches in the correct order if necessary.
However, when testing this replace feature, informing the ".msp" files in the patch template that it should overwrite, the installation is successful and the software works perfectly.
- PatchesToReplace.png (77.5 KiB) Viewed 9672 times
- PatchesToReplace_Installed.png (88.6 KiB) Viewed 9672 times
But, when uninstalling the patch the version downgrade is done, but the software itself does not revert back to the previous version, as expected.
Example scenario:
* Installed version: 21.0.1
- 1st Patch applied: 21.0.1.1
- 2nd Patch applied: 21.0.1.2 (overlapping the previous one)
- 2nd Uninstalled Patch: 21.0.1.2
After uninstalling the 21.0.1.2 patch, the user-visible patch reverts to 21.0.1.1, but the software does not revert to the content of this version, erroneously getting the 21.0.1.2 patch changes.
- PatchesToReplace_Uninstalled.png (89.72 KiB) Viewed 9672 times
Could you help me with this problem?
Best regards,
Lucas