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

Chapter 2: Getting Started
Upgrading from Earlier Versions of InstallShield
dialogs if the target system is running the appropriate code page. However, it displays garbled characters
instead of double-byte characters in those dialogs if the target system is not running the appropriate
code page.
If you create a new Express project in InstallShield 2012 Express Edition, the default setup launcher
type is Unicode. In addition, if you create a new QuickPatch project in InstallShield 2012 Express
Edition, the default update launcher type is Unicode.
If you upgrade an Express project or a QuickPatch project from InstallShield 2008 Express Edition or
earlier to InstallShield 2012 Express Edition, the update launcher type for any existing patch is ANSI.
You can override the type if appropriate.
Dynamic File Links
When you add or modify a dynamic file link in a project, you can specify which component creation
method you want InstallShield to use: a new best practice method or the previously available onecomponent-per-directory
method. These methods are applicable to dynamic file linking in Express
projects.
If you create a new dynamic file link in InstallShield 2012 Express Edition, InstallShield uses the best
practice method by default.
All dynamic file links that are created in InstallShield 2008 Express Edition or earlier use the onecomponent-per-directory
method. If you have a project with dynamic file links and you upgrade it from
InstallShield 2008 Express Edition or earlier to InstallShield 2012 Express Edition, InstallShield
continues to use the one-component-per-directory method for creating the components of those already
present dynamic file links. For any new dynamic file links that you create in the upgraded project, the
best practice method is used by default. For detailed information about the two component creation
methods, as well as guidance on which method you should use, see Determining the Appropriate
Component Creation Method for Dynamically Linked Files.
IIS Web Sites Without Virtual Directories
InstallShield now includes support for installing IIS Web sites without any virtual directories. This
support is available for all new Web sites that are created in new InstallShield 2012 Express Edition
projects. This support is also available if you upgrade a project from InstallShield 2008 Express Edition
or earlier to InstallShield 2012 Express Edition and then add a new Web site.
Note that if you upgrade an InstallShield 2008 or earlier project to InstallShield 2012 Express Edition,
and the project already contains a Web site, the Web site cannot be installed if it does not have any
virtual directories. In order to be able to install the Web site without virtual directories, you must
manually delete it from your InstallShield 2012 Express Edition project, and then re-add it to your
project as a new Web site.
Simplification of QuickPatch Packages
The new Streamline QuickPatch setting on the Advanced tab in a QuickPatch project determines how
InstallShield builds QuickPatch packages. A streamlined QuickPatch package typically has fewer new
subfeatures and custom actions than a non-streamlined QuickPatch package.
In some cases, InstallShield cannot streamline the QuickPatch package. For example, if you configure
the QuickPatch package to remove an installed file, InstallShield cannot streamline it.
When you create a new QuickPatch project, the default value for the Streamline QuickPatch setting is
Yes. However, when you upgrade a QuickPatch project from InstallShield 2008 Express Edition or
earlier to InstallShield 2012 Express Edition, the value for this setting is No. You can change this value if
appropriate. For more information, see Specifying Whether to Streamline the QuickPatch Package.
InstallShield 2012 Express Edition User Guide ISE-1800-UG01 95