Component List problem in maintenance mode

[marmadoc]

Hi InstallAware,

I'm sure you're tired of hearing the same praises for an excellent product, but I'm giving my bit as well, as I'm sure you guys can handle it. Well Done! I'm very impressed!

I am currently evaluating the product and came across the following issue:

Starting from the default Maintenance Mode script with the wizard loop containing the 3 dialogs (maintenance, components tree, start installation) I soon realised I am going to need more logic. So I discarded the wizard loop and implemented a similar structure as the normal installation mode.

So, now I have a number of dialogs after the component selection form to gather user input if a new component is selected during maintenance mode which was not installed originally.

This works fine, except for one thing: If the user makes changes to the selected components list during maintenance mode (e.g. selecting a new component to install) and then in a following dialog cancels the installation, the new component selection is persisted by the install engine. This presents a problem because if the installation is run again (again in maintenance mode) the modified components list is shown which is incorrect since the components have not actually been installed.

I may perhaps incorrectly perceive this as a problem, but it seems as though the install engine persists the Component List immediately after the component selection form.

I'm thinking that this should only be done at the end of installation.

The way I see it one would like to know which components were installed during a successful installation as opposed to which components were selected during a partial or cancelled installation.

I may be missing something here, in which case please guide me in the right direction.

However, if this is by design or not seen as a problem, could you please comment on the situation and maybe give me another perspective?

Thanks in advance!

[CandiceJones]

Hi,

I was able to see this problem easily. I've escalated it for you - you should be hearing from us with a resolution soon!

[marmadoc]

Hi Candice,

I actually know of two workarounds:

1. To use the Save Feature Selection command.
2. To manually save the selection state for each component in persistent variables.

These methods seems cumbersome, but they will work. However, I'm still anxious to hear what the response will be.

Thanks!

[CandiceJones]

We should have a fix for this shortly!

[CandiceJones]

A fix is now available for licensed users. Just log on to your customer account, regenerate and reinstall your license. That's all you need.

If you are not using persistent variables, you are not affected by this problem.

For unlicensed users, trial downloads shall shortly be updated.

[marmadoc]

Thanks for the quick response and fix!

Since I'm still evaluating I can't verify that it works yet, but for one thing, if I had any doubts whether I should buy, the rapid bugfixing and customer support definitely eradicated them completely.

Thanks again!

[CandiceJones]

You're welcome! Please help spread the word
The update is now available for download on the main download page, btw.