Determining Which Installation Project Is Right for You

InstallShield allows you to create different installation projects, including InstallScript and Basic MSI. Deciding which of these two project types is right for you depends upon your experience with InstallShield software and installation development and on your installation and deployment needs.

The Welcome Assistant

InstallShield provides a Welcome Assistant to help you determine which project type is best for your software installation needs. The first time you launch InstallShield, the Welcome Assistant requests information about any previous experience with InstallShield products, your software installation requirements, and your familiarity with various technologies. Based on this information, the Welcome Assistant recommends the project type that better suits your needs.

InstallScript Projects

InstallScript projects use InstallScript to control the installation. It is recommended if you want a highly customized run-time user interface, such as those including multimedia elements. InstallScript installations are generally less desirable to systems administrators because they do not use the Windows Installer database. In general, InstallScript projects are more flexible than Basic MSI projects and are easier to debug.

Have advanced requirements for the user experience (the end-user dialogs).

Prefer authoring the user experience using a procedural language rather than a set of tables.

Want to use InstallShield’s InstallScript engine, with no reliance on Windows Installer.

Are upgrading your project from InstallShield Professional and want to preserve as much of your existing InstallScript code as possible.

Want to use full-screen billboards during the user experience.

Basic MSI Projects

Basic MSI projects use the Windows Installer service to drive the entire installation, including calls to any custom actions (InstallScript, VBScript, JScript, .exe, .dll). It is recommended if your software will be customized by corporate system administrators prior to deployment. It gives them the flexibility to create transforms for the installation package and its associated properties, without repackaging your installation.

Maximize compatibility with administrative tools such as SMS.

Maximize the ability of users or other third parties to customize the installation for redeployment.

Minimize the size of the installation package.

Avoid writing scripting code and want to instead set properties and make table entries.