This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Component non-key files are not removed on upgrade.
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 17, 2010
06:19 PM
Component non-key files are not removed on upgrade.
I have a product installed on a machine. It has the following component (and files):
component1
----file1 (keyfile)
----file2
----file3
I have an newer version of the product that has the same component without the non-key files:
component1
----file1 (keyfile)
After upgrade, file2 & file3 are still on the machine. Is it possible to fix this?
NOTE: Action "RemoveExistingProducts" is run after action "InstallFinalize" in this case.
Thanks in advance!
component1
----file1 (keyfile)
----file2
----file3
I have an newer version of the product that has the same component without the non-key files:
component1
----file1 (keyfile)
After upgrade, file2 & file3 are still on the machine. Is it possible to fix this?
NOTE: Action "RemoveExistingProducts" is run after action "InstallFinalize" in this case.
Thanks in advance!
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 17, 2010
09:27 PM
Is the file1 exactly the same between your old version and new version?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 18, 2010
10:24 AM
Hi,
No, file1 is different. It is an exe file. Both files are versioned. file1 in the new package has a newer version.
Thanks
No, file1 is different. It is an exe file. Both files are versioned. file1 in the new package has a newer version.
Thanks
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 18, 2010
11:18 AM
I suspect that you are running into expected Windows Installer major upgrade behavior when the RemoveExistingProducts action is sequenced after InstallFinalize. In this situation, the updated key file is installed during the InstallFiles action (as it would have been if you were using a minor upgrade), and then at the end of the install MSI is determining that this component does not need to be removed because it is still present in the new version of the product.
Your possible work-around options include the following:
1. Sequence RemoveExistingProducts action in the InstallShield default location of after InstallValidate action (You can also change this same setting in Upgrades View - Upgrade Windows Installer Setup - Major Upgrade Settings.
OR
2. Use the RemoveFile table to remove the files no longer in the component (this approach works in a minor upgrade, so I suspect that it will also work in this case).
OR
3. Use a custom action to delete the files no longer included in the component.
Hope this helps,
Ajay
Your possible work-around options include the following:
1. Sequence RemoveExistingProducts action in the InstallShield default location of after InstallValidate action (You can also change this same setting in Upgrades View - Upgrade Windows Installer Setup - Major Upgrade Settings.
OR
2. Use the RemoveFile table to remove the files no longer in the component (this approach works in a minor upgrade, so I suspect that it will also work in this case).
OR
3. Use a custom action to delete the files no longer included in the component.
Hope this helps,
Ajay
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jun 02, 2010
02:02 PM
OK Thanks!
I thought that was the case, but figured I'd ask anyway.
I thought that was the case, but figured I'd ask anyway.
![](/skins/images/D60DF682EA37BF37032955CE10F3F0BB/responsive_peak/images/icon_anonymous_message.png)