使用Instal Shield如何通过自定义对话框复选框安装应用程序（文件传输，先决条件）

Question

我正在尝试通过创建自定义对话框来安装三个应用程序。在自定义对话框中有复选框和Onclicking复选框，此后接下来我想让我的应用程序进行文件传输，安装基于该复选框的先决条件。我希望这种情况发生所有这三个应用程序。请建议如何做以及如何给条件。

Answer 1

Assuming you're talking about a custom dialog for a Basic MSI, I would suggest the following:

1. Ensure each application in question is part of a separate feature. If you go with the original dialog set, this would potentially let the user select them by feature name, or you could hide them. These features should have meaningful names, along the lines of App1 , App2 , App3 .
2. Ensure your three check boxes are associated with different properties, such as INSTALL_APP_1 , INSTALL_APP_2 , INSTALL_APP_3 . I show public properties here out of habit, but since they will be used in the same sequence (on the same dialog box, even), it's okay to use private properties. And use suffixes more meaningful than 1, 2, 3.
3. Adding multiple control events to the Next or Install button on the dialog box you described. For each feature you want to control this way:
   • Add an AddLocal control event, with an argument of the feature name (eg App1), conditioned to execute when the check box is checked (ie with a condition like INSTALL_APP_1
   • Add a Remove control event, with an argument of the feature name (eg App1), conditioned to execute when the check box is not checked (ie with a condition like NOT INSTALL_APP_1 .

4. If you are going to show this dialog box during maintenance, you should also initialize the values of the check box properties ( INSTALL_APP_1 , etc.) so that merely going past this dialog box doesn't change their installation state. You can use feature-state condition syntax ( !App1 , etc.) to do so in SetProperty custom actions scheduled just before showing the maintenance dialog (eg set property INSTALL_APP_1 to the value 1 with condition !App1=3 ).

5. If these features are shown in a feature selection control, be sure to update the properties accordingly. Do so on the Next button of that dialog using a combination of the feature state and feature action syntaxes. The property should be 1 if the feature is currently installed and not being removed, or is being installed; it should be set to empty ( {} ) otherwise.

This is a lot of steps, but together they help ensure the features will act as a user expects. If he does nothing to change their state, they should persist as previously set. If visible in both the feature selection control and via check boxes, they should act in sync.

As far as prerequisites, if you mean the InstallShield concept of prerequisites, this you can associate prerequisites with the features for those apps. If you just mean other components inside your MSI, those work perfectly well with the features defined in step 1 as well.