i have a install package with registry entrys i made from user input. (without persistent option of property)
The user could change its input in "Maintenance mode" but in this mode the registry values defined with properties in the "Registry" page didnt change.
How can i force to change the registry values in maintenance mode?
In order to achieve this you can go to the Organization page, create a new feature and add to it your registry entries.
In the Feature Properties panel:
- set the "Identifier" or the feature, for example "Registry"
- select the "Not Displayed" option from the "Feature Tree", so it will not be shown in the ConfigureDlg dialog
Go in the Dialog page:
- select the "VerifyReadyDlg" from the Maintenance folder
- click on the "Install" button on the dialog
- add a published event by clicking the "New" button from the "Published Events" tab
- select "Reinstall one or more features" from the newly appeared dialog
- in the "Argument" edit box write the identifier of the feature that contains the registry, in our example "Registry"
- do not modify the "Condition" field and click [OK]
- expand the "MaintenanceTypeDlg" dialog and select the "VerifyRepairDlg" Dialog
- click on the "Repair" button and follow the steps you followed for the "Install" button
- build and run the project
Another thing with "Maintenance" that i want to ask:
I have a "Single .exe Setup with resources inside". The Setup is side by side and generating instances.
I could install three or more instances without problems.
The last instance which was installed has the "enhanced ui" and there are no problems while installing. The other instances in maintenance mode has a different ui with other buttons and all images are without transparency etc.
I think the instances missing the .exe bootstrapper or something else. I think im missing the enhanced ui features.
I'm afraid that this is the normal behavior. When instances from a multiple instance product are upgraded, only the first instance is installed as a major upgrade, the other instances are upgraded using the Windows Installer Minor Upgrades support and that is why the "Resume" dialog is displayed.
i think it is not the "Resume" Dialog which appear.
I made a test project. In one case i have the enhanced ui in maintenance and in the other case (new instance), there is no enhanced ui.
In both cases i start the setup maintenance through the .exe setup file.
Is it possible to have the maintenance mode with enhanced ui in every instance?
This may happen because the "Enhanced User Interface" feature is set to "Only on install" in the "Themes" page, "Settings" tab of your project. Can you set it to "Always" and see if the behavior persists?
It seems that this is an Advanced Installer limitation. An improvement regarding this is already on our TODO list and it will be available in a future version of Advanced Installer. We will notify you as soon as this will be fixed.
I'm afraid that the only workaround is to disable the "Enhanced User Interface" feature and use the Classic theme. Sorry for the inconvenience.