Hi,
This results in confusion since they then need to click on a non disabled item to continue after they disable one (red X).
Perhaps the confusion would be greater if the user is able to set the installation path when selecting a feature which will not be installed (if the feature is not installed, why can you change the installation path?). However, in an Enterprise project you can change the behavior of the Browse button:
- in the "Dialogs" page select the "Browse" button on the "CustomizeDlg" dialog (under "SetupTypeDlg")
- in the "Published Events" tab remove the existing control event
- create two new control events which look like this:
Code: Select all
[_BrowseProperty] APPDIR 1
SpawnDialog BrowseDlg 1
This way the Browse dialog will always be visible. Additionally, you can make the installation path visible even for a feature which will not be installed:
- select the "<The selection's path>" static text control
- in the "Subscribed Events" tab remove the existing events
- in the
Properties pane set the "Text" field to:
- select the "Location" static text control
- remove the event in the "Subscribed Events" tab
Regards,
Cosmin
FOLLOW US
Get the latest news in Application Packaging