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

Chapter 24: View Reference
Organize Your Setup View
Table 24-3: General Settings (cont.)
Setting Description
INSTALLDIR Specify the value of the Windows Installer property INSTALLDIR, which indicates the
destination directory where most of the files of the product will be installed at run time.
The default value is as follows:
[ProgramFilesFolder]My Company Name\My Product Name
Instead of hard-coding a path, you can enter a directory property as part of the path. To
select a directory property, click the ellipsis button (...) in this setting. This enables you
to select the appropriate directory from a list, or to create a new directory within a
predefined directory. Separate further levels of subdirectories with a backslash—for
example, [ProgramFilesFolder]MyApp\Bin.
Windows Logo Guideline: To comply with the Windows logo program, your product's
default destination should be a subfolder of the Program Files folder
([ProgramFilesFolder]), which can vary depending on the system’s locale and user
settings.
For more information, see Setting the Default Product Destination Folder (INSTALLDIR).
Locked-Down Permissions Select the type of permissions that you want to use for securing files, folders, and
registry keys for end users who run your product in a locked-down environment. Available
options are:
• Custom InstallShield handling—InstallShield uses a custom ISLockPermissions
table and adds custom actions to your project to set permissions on the target
system. This option is the default value.
• Traditional Windows Installer handling—InstallShield uses the
LockPermissions table in the .msi database to store permission information for
your product.
It is often more advantageous to use the custom InstallShield handling than the
traditional Windows Installer handling. For example:
• The custom option includes support for many well-known security identifiers (SIDs)
that are not supported by the traditional option.
• The custom option supports the use of localized user names for many well-known
SIDs, unlike the traditional option. With the traditional option, if you try to use a
localized name to set permissions on a non-English system, the installation may fail.
• The custom option lets you specify that you want to deny a user or group from
having the permissions that you are specifying. The traditional handling does not
allow you to do this. That is, with the traditional handling, you can only set specific
permissions; you cannot deny permissions.
This is a project-wide setting that affects all new permissions that you set for files,
folders, and registry keys in your project. If you have already configured some
permissions in your project and then you change the value of this setting, InstallShield
lets you specify whether you want to use the alternate handling method for those
already-existing permissions.
For more information about configuring this setting, see Securing Files, Folders, and
Registry Keys in a Locked-Down Environment.
508 ISE-1800-UG01 InstallShield 2012 Express Edition User Guide