InstallShield summary series InstallShield script Project

I have talked about basic MSI project in the previous article. The difference between them is:

In terms of functions, the InstallShield script project is more elastic and can customize more things. The dialog box can be easily customized and their display sequence has been controlled.

In terms of mechanism, InstallShield script is based on InstallShield installe engine and does not require Windows Installer engine. It supports more InstallShield functions and dialog boxes.

 

The following are some common technical points to understand the InstallShield script project:

1. Maintenance Mode

Oninstallaing ()

It corresponds to the-unistall command. In InstallShield 2009 and earlier versions, selecting "Uninstall" in the control panel triggers this command. However, after InstallShield 2011, uninstall will call

-Removeonly: the first function to respond to this message is onmaintainuibefore (). The default value isCodeWill collaborate with the corresponding products.

 

Removeonly & removeallmode & removeall

Removeonly and removeallmode are both flags, and their values are true or false.

Call removeonly to set removeonly to true, that is, to inform the developer that this is the uninstall mode called through the command line.

By selecting removeall in maintaince Dialog (a value predefined by InstallShield), removeallmode is set to true.

 

Silent Installation

You must first record the installation script, that is, the. ISS file. It should be noted that the installation process must be strictly as described in. ISS; otherwise, the installation will fail. If you have many options during the installation process, you need to record multiple. ISS files.

 

2. Upgrade and install

Corresponding to InstallShield script. During upgrade, note that the merge module may not be updated. No reason is found yet. Currently, we use the walk around und method, that is, modifying the merge modulecomponent ID to complete the upgrade and installation.