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.

Table 18-2: Folder Properties (cont.)<br />

Property Name Description<br />

Chapter 18: Additional Installation Options<br />

Working with Windows Installer Properties<br />

SETUPEXEDIR The SETUPEXEDIR property contains the path to Setup.exe. For<br />

example, if the path to Setup.exe is<br />

C:\MySetups\MyApp\Setup.exe, the value of SETUPEXEDIR is<br />

C:\MySetups\MyApp.<br />

Note: There are two limitations to using SETUPEXEDIR:<br />

• SETUPEXEDIR is set by Setup.exe. If the end user runs the .msi<br />

package directly, SETUPEXEDIR is not set. To account for this, you<br />

could have a dual implementation in your installation—one that uses<br />

SETUPEXEDIR and one that uses SourceDir. You could test for the<br />

existence of SETUPEXEDIR and, if it does not exist, you could<br />

conditionally use your SourceDir implementation.<br />

• SETUPEXEDIR might not be set at uninstallation. If the end user<br />

triggers the uninstallation by running Setup.exe, SETUPEXEDIR is<br />

set. If they run the uninstallation from Add or Remove Programs,<br />

SETUPEXEDIR is not set.<br />

Note that in an uncompressed installation, SourceDir and<br />

SETUPEXEDIR have the same value.<br />

SETUPEXENAME This property identifies the name of the setup launcher file that was<br />

created when the project was built. The installation updates the value of<br />

this property at run time if the setup launcher file was renamed. The<br />

following path identifies the full path to this file:<br />

[SETUPEXEDIR]\[SETUPEXENAME]<br />

SourceDir This property stores the root directory where all the source files are<br />

located.<br />

Caution: If your release consists of an .msi package that is<br />

compressed into a setup launcher and the .msi package is not cached<br />

on the local machine, SourceDir should be referred to during<br />

installation, but not during uninstallation or maintenance. In these<br />

circumstances, the setup image runs from a temporary location that is<br />

removed following installation.<br />

SETUPEXEDIR is an alternative to the directory identifier SourceDir. A<br />

potential problem with using SourceDir is that it points to the location<br />

of the running .msi package. In the case of a compressed installation,<br />

the .msi package is streamed to a temporary location and run from<br />

there. Because of this, the value of SourceDir will be some temporary<br />

location on the end user’s machine, which might not be the value you<br />

want.<br />

TARGETDIR The TARGETDIR property is the location where the Windows Installer<br />

package is copied (and its data files uncompressed) during an<br />

Administrative installation.<br />

<strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong> <strong>User</strong> <strong>Guide</strong> ISE-1800-UG01 351

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

Saved successfully!

Ooh no, something went wrong!