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: Uninstall doesn't seem to call generateOptionsEntries
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
‎Jul 19, 2006
08:25 PM
Uninstall doesn't seem to call generateOptionsEntries
I have a custom dialog (with a generateOptionsEntries event) that I use in uninstall sequence. I generated a response file by using -options-record uninstall.txt, but the only thing written to uninstall.txt were the 2 feature.active entries. The generateOptionsEntries of my custom dialog did not get called. It appears as if generateOptionsEntries events are only called for dialogs that were called during the initial install sequence. How can I get a custom dialog that is only used during uninstall to add it's options to a response file during uninstall?
(2) Replies
‎Jul 21, 2006
03:58 PM
pjbeatty wrote:
I have a custom dialog (with a generateOptionsEntries event) that I use in uninstall sequence. I generated a response file by using -options-record uninstall.txt, but the only thing written to uninstall.txt were the 2 feature.active entries. The generateOptionsEntries of my custom dialog did not get called. It appears as if generateOptionsEntries events are only called for dialogs that were called during the initial install sequence. How can I get a custom dialog that is only used during uninstall to add it's options to a response file during uninstall?
I have gotten this to work before. The generateOptionsEntries method should be called for each panel that's utilized during the uninstall. What does your generateOptionsEntries method look like?
Should have an if/else clause that should check to see if
context.getValueType() == WizardBean.TEMPLATE_VALUEor not (the *not* part is the part you are concerned with, i.e. the part that would be setting the value when running with -options-record, instead of -options-template). After that, make sure you create title, description, and option strings (option string containing the recorded value) and then call
optionEntries.addElement(new OptionsTemplateEntry(title, description, option);where optionEntries is a Vector returned from context.getOptionEntries()
‎Jul 27, 2006
04:30 PM
I have this working for install. Like I said generateOptionsEntries does not get called for a dialog that is in the uninstall sequence. I used my Eclipse debugger to check this. I set a breakpoint, but breakpoint was never reached. Breakpoints set in generateOptionsEntries of custom dialogs that run in install sequence are reached.
Since I see that options are created for features, which also initially run during install, I'm thinking that maybe dialogs are only registered to generate options during install sequence. Then if -options-record is given at uninstall, only those dialogs that ran/registered during install and then run in uninstall have their generateOptionsEntries method called.
In other words, if all my custom dialogs run during install, then all would have their generateOptionsEntries method called during uninstall.
This is just my speculation based on what I've observed from the uninstall response file and setting breakpoints in my debugger.
Since I see that options are created for features, which also initially run during install, I'm thinking that maybe dialogs are only registered to generate options during install sequence. Then if -options-record is given at uninstall, only those dialogs that ran/registered during install and then run in uninstall have their generateOptionsEntries method called.
In other words, if all my custom dialogs run during install, then all would have their generateOptionsEntries method called during uninstall.
This is just my speculation based on what I've observed from the uninstall response file and setting breakpoints in my debugger.