09.12.2012 Views

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

InstallShield 2012 Express Edition User Guide - Knowledge Base ...

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 2: Getting Started<br />

Installation Fundamentals<br />

Table 2-1: Getting Started Road Map (cont.)<br />

Level of Familiarity Top Help Topics<br />

You are an intermediate-level or advancedlevel<br />

user of <strong>InstallShield</strong>.<br />

Installation Fundamentals<br />

An installation, in its simplest terms, is the “package” used to install your files and programs onto your<br />

user’s machine. It is a complete collection of the application files, as well as logic that interacts with the<br />

installer engine. The primary task of any installation is to transfer the application files from the source<br />

medium to the end user’s computer. The complexities of the Windows operating system make it<br />

anything but simple to create an effective, coherent installation without the aid of a utility such as<br />

<strong>InstallShield</strong>.<br />

An installation is divided into three levels: products, features, and components. The following diagram<br />

illustrates this hierarchy:<br />

Figure 2-1: Installation Hierarchy<br />

If you are familiar with <strong>InstallShield</strong>, you may want to review the<br />

following topics:<br />

• Errors and Warnings<br />

A product is the highest level of organization in an installation project. A product is usually one main<br />

application (for example, a word processor) and all of the files and data that the application requires; a<br />

suite of applications may also be a product.<br />

A feature is the smallest installable part of a product, from the end user’s perspective. As the designer of<br />

an installation program, you usually allow the user to choose which features to install and which features<br />

to leave on the source media. In a word processor product, the main executable may be one feature, and<br />

optional dictionaries may be a separate feature. A feature should be self-contained, in the sense that a<br />

feature should not require sibling features. For example, a thesaurus feature should not require a<br />

dictionary feature that the user can choose not to install. However, you can design features to contain<br />

subfeatures, which allow the end user finer control over which files and data to install.<br />

Each feature in a project is made up of one or more components. A component is the smallest installable<br />

part of a product. The <strong>Express</strong> edition of <strong>InstallShield</strong> creates components for you automatically. The<br />

actual breakdown of features into various components is not visible anywhere within the <strong>InstallShield</strong><br />

user interface. In addition, components are invisible to the end user. Each component contains files (and<br />

other resources) with similar properties. For example, all of the files in a component will be installed in<br />

the same directory on an end user’s machine, and all of the files in a component should apply to the<br />

46 ISE-1800-UG01 <strong>InstallShield</strong> <strong>2012</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!