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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 1: <strong>InstallShield</strong> <strong>2012</strong> <strong>Express</strong> <strong>Edition</strong><br />

Target System Requirements<br />

In addition, the Windows Mobile Wizard now enables you to specify configuration XML files for any<br />

Windows Mobile device installations. Previously, only Smartphone device installations could include<br />

configuration XML files.<br />

Registry and File Filtering Enhancements for COM Extraction and Dependency<br />

Scanners<br />

To prevent <strong>InstallShield</strong> from extracting undesired COM data from a COM server, you can edit a new<br />

Filters.xml file that is installed with <strong>InstallShield</strong>. Editing this Filters.xml file enables you to customize<br />

the list of registry keys that will be excluded from COM extraction.<br />

The Filters.xml file also now lists files that the Static, Dynamic, and Visual Basic dependency scanners<br />

will exclude or include. Previously, two different files—<strong>User</strong>scan.ini and Iswiscan.ini—were used to list<br />

excluded and included files.<br />

For more information, see:<br />

• Filtering Registry Changes for COM Extraction<br />

• Filtering Files in Dependency Scanners<br />

Enhanced Start Page<br />

The list of recently opened projects that are displayed on the Start Page now includes a column that<br />

shows the project type. In addition, the maximum number of projects that are listed has been increased<br />

from four to eight.<br />

Workaround for Windows Installer Issue with Upgrades and Assemblies<br />

By default, upgrades that are created in the Upgrade Paths view are configured to remove the earlier<br />

version of the product before installing the new version. That is, the RemoveExistingProducts action is<br />

scheduled before the InstallFinalize action. This default sequencing behavior may cause a problem if the<br />

product includes an assembly that is installed to the global assembly cache (GAC): after the upgrade is<br />

applied, the assembly may be missing from the GAC. The issue occurs because Windows Installer cannot<br />

properly reference count the assembly; therefore, it is removed but not reinstalled during the upgrade.<br />

To work around this Windows Installer issue, you can now configure your project in <strong>InstallShield</strong> so that<br />

the new version of your product is installed before the earlier version is removed.<br />

To learn more, see Preventing the Removal of Assemblies from the Global Assembly Cache During<br />

Upgrades.<br />

Target System Requirements<br />

You can use <strong>InstallShield</strong> to rapidly build, test, and deploy installations that target Windows-based<br />

systems and mobile devices.<br />

Requirements For Desktop Computers<br />

Operating System<br />

Target systems must meet the following minimum operating system requirement:<br />

• Windows 2000<br />

34 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!