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
- :
- Re: Execute Custom Action During Minor 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
Aug 14, 2008
08:25 AM
Execute Custom Action During Minor Upgrade
I thought I understood how conditions on custom actions worked, but apparently I am missing some detail.
I have a custom action in my installation that has a contion of "&MyFeature = 3". During a new install, the custom action runs when the MyFeature is installed, as expected. However, during a Minor Upgrade, the custom action is NOT run, though I expected it would be. From the installation log I can see that:
Feature: MyFeature; Installed: Advertise; Request: Reinstall; Action: Reinstall
I would have thought that when the Action State is set to Reinstall, the &MyFeature would equate to 3 - it is to be installed. Is that not the case? Is there a different value I should be using in the condition to catch when the MyFeature is being Reinstalled?
(As an aside, I did notice that the MyFeature's Install State is listed as Advertised; I expected that to be Local, but maybe because the feature only includes references to merge modules it shows up as Advertised? I do not think that relates, as I have this same issue with a custom action for another feature that is listed as local. Just another Windows Installer curiosity.)
Thanks!
Robert O'Brion
AT&T
I have a custom action in my installation that has a contion of "&MyFeature = 3". During a new install, the custom action runs when the MyFeature is installed, as expected. However, during a Minor Upgrade, the custom action is NOT run, though I expected it would be. From the installation log I can see that:
Feature: MyFeature; Installed: Advertise; Request: Reinstall; Action: Reinstall
I would have thought that when the Action State is set to Reinstall, the &MyFeature would equate to 3 - it is to be installed. Is that not the case? Is there a different value I should be using in the condition to catch when the MyFeature is being Reinstalled?
(As an aside, I did notice that the MyFeature's Install State is listed as Advertised; I expected that to be Local, but maybe because the feature only includes references to merge modules it shows up as Advertised? I do not think that relates, as I have this same issue with a custom action for another feature that is listed as local. Just another Windows Installer curiosity.)
Thanks!
Robert O'Brion
AT&T
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 11, 2008
03:27 PM
Did you ever find out how to make this work?
Thanks!
Simon Morton
WSI Corporation
Thanks!
Simon Morton
WSI Corporation
![](/skins/images/B841502EC6C60E3ACD181F0696AD21B9/responsive_peak/images/icon_anonymous_message.png)