09.12.2012 Views

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

InstallShield 2012 Spring Express Edition User Guide

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 8: Organizing Files for Your Installation<br />

Including Redistributables in Your Installation<br />

Setup Prerequisites vs. Feature Prerequisites<br />

An <strong>InstallShield</strong> prerequisite that is run before the main installation’s user interface sequence begins is<br />

called a setup prerequisite. Setup prerequisites are useful for base applications and technology<br />

frameworks that must be installed for all configurations of the installed product or that provide<br />

functionality that is used during the installation itself. When you add an <strong>InstallShield</strong> prerequisite to a<br />

project, it is the setup prerequisite type of <strong>InstallShield</strong> prerequisite by default.<br />

The <strong>Express</strong> project type enables you to associate <strong>InstallShield</strong> prerequisites with features in your main<br />

installation. When an <strong>InstallShield</strong> prerequisite is associated with one or more features, it is called a<br />

feature prerequisite. Feature prerequisites are installed after an end user has chosen which features to<br />

install; like merge modules, a feature prerequisite is installed only if one or more of the features that<br />

contain it are installed. Thus, feature prerequisites are useful for applications or components that are<br />

used by only some configurations of the installed product and are not used during the installation itself.<br />

Review the following sections for more information that will help you determine which type of<br />

<strong>InstallShield</strong> prerequisite will best fit your requirements.<br />

Special Considerations for Setup Prerequisites<br />

Following are some tips to consider if you are including one or more setup prerequisites in your project.<br />

.NET Framework Requirements<br />

If your product requires that the .NET Framework be installed on the target system, you may include the<br />

.NET Framework redistributable to your project. If the target system does not have the .NET<br />

Framework, it is installed during your installation. For more details, see Adding .NET Framework<br />

Redistributables to Projects.<br />

<strong>Edition</strong>: <strong>InstallShield</strong> Premier <strong>Edition</strong> and <strong>InstallShield</strong> Professional <strong>Edition</strong> enable you to configure an <strong>InstallShield</strong><br />

prerequisite so that it is installed either before or after any installation of the Windows Installer engine and the .NET<br />

Framework.<br />

Launching the .msi Package Instead of the Setup Launcher<br />

If your installation includes a setup prerequisite and end users launch the .msi package for your product<br />

directly, rather than launch the Setup.exe setup launcher, the setup prerequisite installation will not<br />

run. If the prerequisite is not already present on a target system, your product may not work as expected.<br />

This scenario may occur if you build an uncompressed release, where the .msi package is not streamed<br />

into the Setup.exe file.<br />

Special Considerations for Feature Prerequisites<br />

Following are some tips to consider if you are including one or more feature prerequisites in your<br />

project.<br />

Windows Installer Requirements<br />

If your project includes a prerequisite that installs the Windows Installer, the prerequisite should be a<br />

setup prerequisite, not a feature prerequisite. That is, this prerequisite should not be associated with a<br />

feature.<br />

174 ISE-1900-UG00 <strong>InstallShield</strong> <strong>2012</strong> <strong>Spring</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!