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

Chapter 1: InstallShield 2012 Express Edition
Launching InstallShield with vs. Without Administrative Privileges
requires administrative privileges, since InstallShield writes the information to a per-machine
location in the registry. Therefore, the All Users location on that tab is disabled if you are running
InstallShield without administrative privileges.
• Ability to specify All Users locations for merge modules—The Merge Module Options tab on the
Options dialog box is where you specify the folders that contain the merge modules that should be
displayed in the Redistributables view. Modifying the All Users location on that tab requires
administrative privileges, since InstallShield writes the information to a per-machine location in the
registry. Therefore, the All Users location on that tab is disabled if you are running InstallShield
without administrative privileges.
• Ability to edit the locations for Regasm.exe and InstallUtilLib.dll—The .NET tab on the Options dialog
box is where you specify the locations of Regasm.exe and InstallUtilLib.dll files, which are utilities
that are included with the .NET Framework. These utilities are used for COM interop and .NET
custom actions. Modifying these locations on the .NET tab requires administrative privileges, since
InstallShield writes the information to a per-machine location in the registry. Therefore, these
location settings on that tab are disabled if you are running InstallShield without administrative
privileges.
• Ability to specify the frequency for checking for InstallShield updates—The Check for software
updates option on the Updates tab of the Options dialog box is where you specify how often you
want InstallShield to check for software updates. Modifying the frequency on that tab requires
administrative privileges, since InstallShield writes the information to a per-machine location in the
registry. Therefore, the Check for software updates option on that tab is disabled if you are
running InstallShield without administrative privileges.
If you switch between full Administrator and non-Administrator contexts and you use mapped-drive
locations in your projects, you may encounter issues. For example, if you map a drive letter to a shared
network folder through Windows Explorer without administrative privileges, you can access this drive
letter in a non-administrative instance of InstallShield, but not in an administrative instance. Likewise,
if you map a drive letter to a shared network folder through Windows Explorer with administrative
privileges, you can access this location in an administrative instance of InstallShield, but not in a nonadministrative
instance. Thus, if you want to reference network locations in your project, consider using
UNC paths (such as \\server\share) or mapping drive letters both with and without administrative
privileges.
Note that if you are using InstallShield from within Visual Studio, you may not have administrative
privileges. By default, if you launch Visual Studio by double-clicking its shortcut on a Windows Vista or
later system, you will not have administrative privileges.
Task To run InstallShield from within Visual Studio with administrative privileges on a Windows Vista or later system:
1. On the Start Menu, right-click the Visual Studio shortcut and then click Run as administrator.
2. Create a new InstallShield project or open an existing one. For more information, see one of the
following:
• Creating InstallShield Projects in Microsoft Visual Studio
• Opening InstallShield Projects in Microsoft Visual Studio
38 ISE-1800-UG01 InstallShield 2012 Express Edition User Guide