It is recommended only for advanced users.
Because this project type uses two different engines, it is more complex than pure InstallScript or Basic MSI installation projects. Embedded UI Handler for InstallScript MSI Installations. This option also has some limitations that require careful planning if you decide to use this style.įor detailed information about these two styles, see Using the InstallScript Engine as an External vs. This option requires Windows Installer 4.5 on the target machine. The Windows Installer also runs the Execute sequence of the. The Windows Installer calls the InstallScript engine to display the UI. For this style, InstallShield embeds the InstallScript engine within the. New style-This style lets you use the InstallScript engine as an embedded UI handler for your InstallScript MSI installation. The setup launcher serves as a bootstrap application that initiates the InstallScript engine to display the UI and run the InstallScript code, and the Windows Installer to run the Execute sequence of the. With this style, your installation must include a Setup.exe setup launcher. Traditional style-This style lets you use the InstallScript engine as an external UI handler for your InstallScript MSI installation. In addition, InstallShield offers two different styles for the UI of InstallScript MSI installations: The advantage of using the InstallScript engine for the UI is that it offers support for highly customized run-time dialogs. The InstallScript engine serves as the custom user interface (UI) handler of the installation. This is the sequence that typically modifies the target system. 
The Windows Installer engine runs the standard Execute sequence of the.
InstallScript MSI installations use two different installer engines: InstallScript MSI Installation Projects InstallScript MSI Installation Projects
0 kommentar(er)
