See similar issue in the context of WiX.įor a convenient chart of custom action conditions please see this PDF from Flexera (makers of InstallShield). Iīelieve IS_MAJOR_UPGRADE is valid in the installing setup, but Is not true in the installing setup, only in the uninstalling setup. However, you should be aware that the condition UPGRADINGPRODUCTCODE I would prefer the standard, Windows Installer property. Your condition of IS_MAJOR_UPGRADE should work, but you can also use UPGRADINGPRODUCTCODE which is the built-in condition in Windows Installer, the former is InstallShield's own, custom condition I believe. In other cases you should insert the custom action into both sequences - it all depends on what it is doing. Is it making changes to the system, or is it just displaying information or requesting user input? If your custom action makes changes to the system it should be inserted in the InstallExecuteSequence and not in the InstallUISequence at all (no changes should be made to a system from the UI sequence). We need to know what your action is doing to provide correct advice. Technical terms the whole InstallUISequence is skipped, and only the Inserted in the InstallUISequence sequence will never run - in This means there is no GUI and the actions you have When a setup is uninstalled as part of a major upgrade it runs in silent mode.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |