WiX Toolset
How to prevent obsolete msp patches from installing #6280
-
|
I’ve got an MSI that I’m going to generate .msp patches for as hotfixes are necessary. The patches will be cumulative (like the following)… Release 1.0.0 MSI If a customer installs the MSI + hp1 + hp2 and then accidentally tries to re-install hp1 it seems like msiexec will consider hp1 and hp2, notice that hp1 is obsolete, and simply re-install the MSI + hp2 patch. I’d like it to actually exit with some error saying that hp1 is obsolete and not perform any installation. How would this be possible? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Not that this is an answer, but I would recommend against trying to fight the behavior here. The Windows Installer's design supports scenarios like Patch1 is a Day0 fix and Patch2 is a bug fix plus the Day0 fix. Allowing the user to install Patch1 while Patch2 is present ensures the user can remove Patch2 (should the bug fix break them) but still be protected for the Day0 fix. In the end, I expect fighting the behavior is going to be more trouble than it's worth. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply |
Beta Was this translation helpful? Give feedback.
Not that this is an answer, but I would recommend against trying to fight the behavior here. The Windows Installer's design supports scenarios like Patch1 is a Day0 fix and Patch2 is a bug fix plus the Day0 fix. Allowing the user to install Patch1 while Patch2 is present ensures the user can remove Patch2 (should the bug fix break them) but still be protected for the Day0 fix.
In the end, I expect fighting the behavior is going to be more trouble than it's worth.