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.

Chapter 2: Getting Started<br />

Upgrading from Earlier Versions of <strong>InstallShield</strong><br />

• If Netscape 6 or 7 was the default browser, the Netscape 4 settings were used. If Netscape 8 or 9 was<br />

the default browser, the system (Internet Explorer) settings were used.<br />

• If Netscape 4 settings were used, only the proxy server list was read and imported correctly. The<br />

proxy bypass list was read, but it was not imported correctly.<br />

• Non–Internet Explorer 4 compatible settings such as the auto-proxy script setting were not<br />

imported.<br />

• The method that the installation used for determining the default browser was not compatible on<br />

Windows Vista. Therefore, on Windows Vista systems, an installation may not have detected the<br />

default browser correctly.<br />

Rollback Support for Windows Mobile Device Installations<br />

<strong>InstallShield</strong> now has support for rolling back a Windows Mobile–powered device installation that is<br />

included in a desktop-to-device installation if appropriate. This support is made possible through a<br />

built-in <strong>InstallShield</strong> custom action called RollbackCEApps.<br />

With this new custom action, if an end user clicks the Cancel button during the installation of a product<br />

for a Windows Mobile–powered device, the installation is rolled back, and any associated .ini files, .cab<br />

files, and .ico files are deleted from the target machine.<br />

When you add a Windows Mobile–powered device installation in the Mobile Devices view of a new<br />

<strong>Express</strong> project in <strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong>, <strong>InstallShield</strong> automatically adds the<br />

RollbackCEApps custom action to your project.<br />

<strong>InstallShield</strong> also adds this custom action if you upgrade an <strong>Express</strong> project that already has a Windows<br />

Mobile–powered device installation in the Mobile Devices view from <strong>InstallShield</strong> 2008 <strong>Express</strong> <strong>Edition</strong><br />

or earlier to <strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong>.<br />

Changes for Windows Mobile Support in <strong>Express</strong> Projects<br />

<strong>Express</strong> installations that include installations for Windows Mobile–powered devices no longer require<br />

the installation to be launched with elevated privileges on Windows Vista systems; elevated privileges<br />

are now required only for the Execute sequence.<br />

If you have previously worked around the issue by setting the Required Execution Level setting on the<br />

Setup.exe tab for the release to the Administrator option, you can now set it to Invoker.<br />

Changes that Affect New Projects but Not Upgraded Projects<br />

This section describes changes to <strong>InstallShield</strong> that may affect new projects but not projects that are<br />

upgraded from earlier versions. Note that you may need to make manual changes to upgraded projects.<br />

Ability to Create Unicode Versions of the Setup.exe and Update.exe Bootstrappers<br />

<strong>InstallShield</strong> now enables you to specify whether you want to create a Unicode version or an ANSI<br />

version of the Setup.exe setup launcher for a project. Previously, if your project included a setup<br />

launcher, <strong>InstallShield</strong> always built an ANSI version; it did not include support for building a Unicode<br />

version.<br />

A Unicode setup launcher can correctly display double-byte characters in the user interface of the setup<br />

launcher, regardless of whether the target system is running the appropriate code page for the doublebyte-character<br />

language. An ANSI setup launcher displays double-byte characters in the setup launcher<br />

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

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

Saved successfully!

Ooh no, something went wrong!