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.

Term Definition<br />

package code The globally unique identifier for an installation package. See also globally unique identifier<br />

(GUID).<br />

panel A window within a wizard that contains one or more related settings that an end user can<br />

configure. See also wizard.<br />

parent/child<br />

installation<br />

See nested installation.<br />

patch A special type of installation package that contains just the bits and portions of the<br />

application that is necessary to either update the application’s files and installation to a<br />

specific version or to fix a bug in an earlier version.<br />

Glossary<br />

patch file A patch package used for patching. A patch package (.msp) file contains the transforms and<br />

instructions necessary for upgrading one or more installed versions of a product. Windows<br />

Installer uses a patch package to patch local or administrative installations. A patch package<br />

does not include a database like a regular installation package. Instead it contains at<br />

minimum one database transform that adds patching information to the database of its target<br />

installation package. The installer uses this information to apply the patch files that are stored<br />

in the cabinet file stream of the patch package.<br />

patching The method of updating an installation that replaces only the bits being changed rather than<br />

the entire application. This means that end users can download a patch for a product that is<br />

much smaller than the entire product.<br />

path In a computer operating system, a path is the route through a file system to a particular file.<br />

A path name is the specification of that path. Each operating system has its own format for<br />

specifying a path name. The DOS, Windows, and OS/2 operating systems use the following<br />

format: driveletter:directorynamesubdirectorynamefilename.suffix. UNIX-based<br />

systems use the following format: /directory/subdirectory/filename.<br />

path variable A variable that represents a location that can be defined once in a central location so that it is<br />

not necessary to change every source file’s path each time that the project is moved or the<br />

folder structure is changed. You can instead use path variables to define commonly used<br />

paths once, and they are used during the development of your installation project. These<br />

paths do not apply to the target machines where the application is being installed. Rather,<br />

they are used to link to source files that need to be included in your installation project. When<br />

the project is built, those links are evaluated and the files they point to are built into the<br />

installation package.<br />

PKCS See public-key cryptography standards.<br />

platform The operating system for which the installation program is intended. An installation<br />

technology may be limited to creating installations for a specific platform(s).<br />

preview mode Mode for viewing the design of the user interface, or the current appearance of dialog and<br />

billboards. Preview mode is a term used in Windows Installer.<br />

product The actual application to be installed or uninstalled.<br />

product code A string that uniquely identifies a product.<br />

progress bar The visual indication of the progress of an executable file.<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 727

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

Saved successfully!

Ooh no, something went wrong!