This post is kind of an offshoot to..


Something is wrong with how the Major Upgrade process is acting. I don't know if its a bug, a missing setting in the Upgrades view in IS or what.

Here's the Scenario....

This takes into account that we have a bad versioned file in our latest release (version < what was deployed with earlier release(s)). This condition is good for this testing.

I install the latest release with no upgrade of previous versions and the file is installed and its shortcut created, which is to be expected.

I install a previous version then uninstall it MANUALLY and install the latest version. Again, the file is placed and the shortcut created, also expected.

Now, I install previous version and run install for the latest, which has RemoveExistingProducts sequenced after InstallValidate. This will remove old prodcucts first. This does appear to happen, but when the latest gets installed, the badly versioned .exe in question does not get installed, hence no shortcut. NOT expected.

What is going on here? I would expect the Major Upgrade to act in the same fashion as the manual removal of the previous version scenario. There should be nothing governing what is placed with the latest release once the old release removed. Why does this not seem to be the case? Is there a setting in InstallShield I'm missing? Is this a bug? Is there some facet of Major Upgrades that I am unaware of?

This concerns me greatly because we rely on Major Upgrades to update our Client workstation application.

PLEASE HELP. Should I contact InstallShield support on this one?

Thanks in Advance!!
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Personally, I wouldn't care and would simply add the rogue file to the RemoveFile table with the attribute set so that it gets removed on uninstall.

For comepleteness, though, what do the various version numbers look like. That is: what the new version number is, what the previous version number should have been and what the previous version number actually is.
Answered 02/10/2011 by: VBScab
Red Belt

Please log in to comment
what does your install log tell you about the component that contains the exe

they'll be a line something like this

MSI (s) (48:9C) [09:56:25:597]: Component: YOUREXECOMPNAME; Installed: Absent; Request: Local; Action: Local
Answered 02/10/2011 by: timmsie
Fourth Degree Brown Belt

Please log in to comment