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.

Task Selecting the locked-down permission type for a project:<br />

1. In the View List under Organize Your Setup, click General Information.<br />

2. In the Locked-Down Permissions setting, select the appropriate option:<br />

Chapter 7: Specifying Installation Information<br />

Configuring General Project Settings<br />

• Custom <strong>InstallShield</strong> handling—<strong>InstallShield</strong> adds a custom table and custom actions to your<br />

project to set permissions on the target system. This is the default value.<br />

• Traditional Windows Installer handling—<strong>InstallShield</strong> uses the LockPermissions table in the<br />

.msi database to store permissions information for your product.<br />

For a detailed comparison of these two options, see Securing Files, Folders, and Registry Keys in a<br />

Locked-Down Environment.<br />

The next time that you configure permissions for a file, folder, or registry key in your project,<br />

<strong>InstallShield</strong> uses the locked-down permission type that you selected:<br />

• If you selected the traditional Windows Installer handling option, <strong>InstallShield</strong> uses the<br />

LockPermissions table in your project.<br />

• If you selected the custom <strong>InstallShield</strong> handling option, <strong>InstallShield</strong> uses the<br />

ISLockPermissions table in your project; <strong>InstallShield</strong> also adds the ISLockPermissionsCost and<br />

ISLockPermissionsInstall custom actions to your project.<br />

If you change the value of the Locked-Down Permissions setting but your project already contains<br />

permission settings for files, folders, or registry keys, <strong>InstallShield</strong> displays a message box that lets you<br />

specify whether you want to migrate the permission data to the appropriate table. If you choose to<br />

migrate the data, <strong>InstallShield</strong> moves the data to the table that corresponds with the option that you<br />

selected; if you are switching from the custom <strong>InstallShield</strong> handling option to the traditional Windows<br />

Installer handling option, <strong>InstallShield</strong> also deletes the ISLockPermissionsCost and<br />

ISLockPermissionsInstall custom actions from your project.<br />

Specifying Whether Windows Installer Installations Should Be<br />

Logged<br />

<strong>InstallShield</strong> enables you to specify on a project-wide basis whether Windows Installer 4.0 or later<br />

should log your installation. You can also customize the types of messages that are logged.<br />

Task To specify project-wide logging information for Windows Installer 4.0 or later:<br />

1. In the View List under Organize Your Setup, click General Information.<br />

2. Click the Create MSI Logs setting, and then click the ellipsis button (...). The Logging Options<br />

for Windows Installer 4.0 and Later dialog box opens.<br />

3. Select the appropriate option. If you select the custom option, enter the MsiLogging value.<br />

For a list of valid parameters for the MsiLogging value, see MsiLogging Property in the Windows<br />

Installer Help Library.<br />

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

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

Saved successfully!

Ooh no, something went wrong!