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.

8<br />

Organizing Files for Your Installation<br />

The primary task of an installation is to transfer files from your distribution media to your end user’s<br />

hard drive. In an <strong>InstallShield</strong> installation, files are organized in a hierarchy: files are included in<br />

features (and optionally subfeatures), and features are associated with setup types.<br />

At run time, your end user simply selects the setup type—or, if you allow it, the features and<br />

subfeatures—that he or she wishes to install.<br />

A file often relies on functions in other files to perform a task. However, you may not be aware of all<br />

these other files—known as dependencies—when you include your application’s files in your project. To<br />

help you identify dependencies, <strong>InstallShield</strong> offers three dependency scanners that automatically add<br />

these files to your project.<br />

In addition to including individual files in your project, you can also include redistributables<br />

(<strong>InstallShield</strong> prerequisites, merge modules, and objects), which contain logic and files needed to install<br />

distinct pieces of functionality. For example, to include the Java Runtime Environment (JRE) files in<br />

your installation, you can add the <strong>InstallShield</strong> prerequisite for JRE to your installation project.<br />

Designing Installations<br />

A feature is the smallest separately installable piece of your product from the end user’s standpoint.<br />

Individual features are visible to end users when they select a Custom setup type during installation.<br />

Features<br />

Features are the building blocks of an application from the end user’s perspective. Each feature<br />

represents a specific piece of functionality for your product—such as the help files. End users should be<br />

able to install and uninstall discrete features of your product.<br />

For example, an end user with limited hard drive space could elect not to install a product tutorial. If the<br />

user subsequently purchases another computer or frees resources on an existing one, the previously<br />

uninstalled product tutorial could then be installed.<br />

You should separate your application into features that correspond to functionality of your application<br />

and that can be available in or removed from different setup types.<br />

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

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

Saved successfully!

Ooh no, something went wrong!