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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Table 24-3: General Settings (cont.)<br />

Setting Description<br />

Chapter 24: View Reference<br />

Organize Your Setup View<br />

DATABASEDIR Specify the default destination folder for all of your application’s database files.<br />

Note: When you are specifying a destination folder for your application’s database files,<br />

you cannot include a space after the closing square bracket (]), or before or after a<br />

backslash (\). For example, the following paths are not valid:<br />

[ProgramFilesFolder] \MyApp\Bin<br />

[ProgramFilesFolder]MyApp\ Bin<br />

It is important to note when using an installer folder property such as DATABASEDIR<br />

that you are specifying a default value. An end user could change this value by setting a<br />

property when launching Msiexec.exe at the command line or by selecting a new<br />

destination folder for a feature in the Database Folder dialog.<br />

Default Font To select the font that you want your installation to use in its user interface, click the<br />

ellipsis button (...) in this setting. If you do not select a font, the installer uses the default<br />

system font.<br />

ALLUSERS Specify how the Windows Installer property ALLUSERS should be set in your project.<br />

The ALLUSERS property specifies whether Windows Installer should attempt to perform<br />

a per-machine or per-user installation. Valid options are:<br />

• ALLUSERS="" (Per-user installation)—Windows Installer performs a per-user<br />

installation, and the configuration information is stored in the user’s personal profile.<br />

• ALLUSERS=1 (Per-machine installation)—If the value of ALLUSERS is set to 1,<br />

Windows Installer attempts a per-machine installation. For per-machine installations,<br />

configuration information such as shortcuts and registry entries are stored in the All<br />

<strong>User</strong>s profile.<br />

On Windows Vista and later systems, if <strong>User</strong> Account Control is enabled and the<br />

user does not have administrative privileges, the user must be able to provide<br />

administrative credentials in order to install the product.<br />

On other systems, if the user does not have administrative privileges, the<br />

installation displays an error message and exits.<br />

• ALLUSERS=2 (Per-user or per-machine installation)—Windows Installer<br />

attempts to perform a per-machine installation on Windows Vista and later systems.<br />

On earlier platforms, if the user has administrative privileges, Windows Installer<br />

attempts to perform a per-machine installation; otherwise, Windows Installer<br />

performs a per-user installation.<br />

The default value for all new projects is ALLUSERS=1 (Per-machine installation).<br />

Note: The value that you specify here for ALLUSERS could be overwritten at run time.<br />

For more information, see Per-<strong>User</strong> vs. Per-Machine Installations.<br />

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

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

Saved successfully!

Ooh no, something went wrong!