Viewing Shared Registry Resources; Special Registry Keys; Ini Files Page - Symantec WINDOWS INSTALLER EDITOR 7.0 SP2 - REFERENCE FOR WISE INSTALLATION STUDIO V1.0 Installation Manual

Viewing Shared Registry Resources

Special Registry Keys

INI Files Page

Windows Installer Editor Reference
b. Enter or select a User name.
c. Click OK.
The domain and user names appear in the upper list box, and the list of permissions
is enabled.
3. To set permissions, mark the check boxes.
You can add multiple users.
Requires a repository connection.
The Shared Resources tab on the Registry Details dialog box displays all packages in the
Software Manager database that use a specific registry key and value. This lets you
ensure that the registry keys that are set by your current application will not conflict
with keys set by other packages.
You also can view shared registry resources in a report format.
See Generating Shared Resource Reports
To view shared registry resources
1. Double-click a registry value on the Registry page in Installation Expert or on the
Components or Features tab in Setup Editor.
The Registry Details dialog box appears.
2. Click the Shared Resources tab.
See also:
Using a Wise Package Studio Repository
Registry Page on page 161
In addition to the standard top-level registry keys, a special registry key named
HKEY_USER_SELECTABLE is provided. Depending on the operating system, during
installation an end user can install an application for the current user only or for all the
users of the computer. Registry changes under this key are made to either
HKEY_CURRENT_USER or HKEY_LOCAL_MACHINE, based on the end user's choice
during installation.
Windows Installer itself also provides registry keys with special functionality. (Example:
You can install a key named AlwaysInstallElevated to force Windows Installer
installations to always install with elevated privileges.) For a list of these special keys,
see User Policies and Machine Policies in the Windows Installer SDK Help.
Use the INI Files page to:
Update the contents of an existing .INI file, such as System.ini.
Create an .INI file and write installation properties to it.
Assembling an Installation
on page 31.
on page 29
170