I am currently working on a new Version of a Setup (3.4.0) where several new input parameters (in this case: an additional path) were introduced. Now, during upgrade, I want to check whether the version I am updating from is < 3.4.0 and show an additional dialog to force the user to input the new path. However, I'd like to skip this step when I'm updating from >= 3.4.0 (at some point in the future, at least), because the path should already be there in those cases. The only property that sounded remotely correct during an upgrade attempt with /L*v logging was "VersionHandler", but its value "3.01" never appears anywhere in my old Setup (nor does it match the old Version number of 3.3.0). Is there a property supplied by default that I can use, or do I have to roll my own? The Setup is a Basic MSI one; I know how to skip Dialogs based on Property Values and I could even use InstallScript to set my own Property based on a few method calls - conversion to an InstallScript Setup is not feasible at this point. ... View more

I have a Basic MSI Setup which does some file modifications (plain-text config file, no XML unfortunately) which has to receive a few values entered by the user. This is done using InstallScript called at the end of the Exec Sequence, "After InstallFinalize" - this works in general. Now I noticed that something is wrong during Upgrades...the values are supposed to be entered by the user, while the Upgrade does not ask for any input. As a result, the config file was overwritten with its default values - this should be disabled. After some playing around (someone suggested "AND RESUME" over here), it seems I even broken it for Modify and Install itself, because the condition never applies now. This is what I have right now: Function Name | ModifyConfig Return Processing | Synchronous In-Script Execution | Immediate Execution Execution Scheduling | Always execute Install Exec Sequence | After InstallFinalize Install Exec Condition | (&Server = 3 OR !Server = 3) AND NOT RESUME AND NOT PATCH AND NOT REMOVE Server is the Feature which triggers the config file modification; it should run when Server is either to be installed (in case of &Server = 3, applies to Installation) or already installed (in case of !Server = 3, applies to Modify). Adding this Resume/Patch/Remove thing apparently broke it afterwards (by chance, it does apply to Upgrade scenarios since the latter 3 conditions just evaluate to false, by coincidence doing what i want). Some testing revealed that Resume/RESUME and Patch/PATCH are not set (or not evaluating to true; unless they use some other casing) when doing either Upgrade or Modify. Since the condition is obviously wrong, could anyone shed some light on how it should be done correctly? ... View more