Upgrading Projects from InstallShield 2010 Express Edition or Earlier

InstallShield 2012 Spring Express Edition

The following information describes possible upgrade issues that may occur when you upgrade projects that were created with InstallShield 2010 Express Edition and earlier to InstallShield 2012 Spring Express Edition. It also alerts you to possible changes in behavior that you may notice between new InstallShield 2012 Spring Express Edition projects and projects that are upgraded from InstallShield 2010 Express Edition or earlier to InstallShield 2012 Spring Express Edition.

General Information about Upgrading Projects that Were Created in Earlier Versions of InstallShield

If you use InstallShield 2012 Spring Express Edition to open a project that was created with an earlier version, InstallShield 2012 Spring Express Edition displays a message box that asks you if you want to convert the project to the new version. If you reply that you do want to convert it, InstallShield creates a backup copy of the project with a file extension such as .770 before converting it. Delete the .770 part from the original project's file name if you want to reopen the project in the earlier version of InstallShield. Note that you cannot open InstallShield 2012 Spring Express Edition projects in earlier versions of InstallShield.

You can upgrade projects that were created with the following versions of InstallShield Express Edition to InstallShield 2012 Spring Express Edition: InstallShield 2010 Express Edition and earlier, InstallShield 12 Express Edition and earlier and InstallShield Express 5 and earlier. Note that projects that were created with InstallShield MultiPlatform or InstallShield Universal cannot be upgraded to InstallShield 2012 Spring Express Edition.

Changes that Affect All Projects (New and Upgraded Projects)

This section describes changes that affect both new projects and projects that are upgraded from earlier versions of InstallShield.

End of Integration Support for Visual Studio 2003 and Earlier

If you want to create, edit, and build your InstallShield projects directly within Visual Studio, you must use Visual Studio 2005 or later. InstallShield can no longer be integrated with Visual Studio 2003 or earlier.

InstallShield Builds Only Unicode Versions of Setup.exe and Update.exe; Ability to Create ANSI Versions Is No Longer Available

Now all Setup.exe and Update.exe files that are built in all project types in InstallShield are Unicode. This applies to all new Express and QuickPatch projects that you create in InstallShield 2012 Spring Express Edition. It also applies to all projects that you have upgraded from earlier versions of InstallShield to InstallShield 2012 Spring Express Edition. Therefore, the settings that previously enabled you to specify whether you wanted to build a Unicode version or an ANSI version of the setup launcher have been removed:

The Setup Launcher Type setting on the Setup.exe tab for a release in the Releases view has been removed from Express projects.
The Update Launcher Type setting was removed from the Advanced tab in the Build Settings area of the General Information view of QuickPatch projects.

New Name for the Postbuild Tab in the Releases View

The Postbuild tab, which is one of the tabs that InstallShield displays when you select a release in the Releases view, has been renamed. It is now called the Events tab. This change is reported for informational purposes.

Changes that Affect New Projects but Not Upgraded Projects

This section describes changes to InstallShield that may affect new projects but not projects that are upgraded from earlier versions. Note that you may need to make manual changes to upgraded projects.

Changing Design-Time and Build-Time Locations of Existing InstallShield Prerequisites in Existing Projects

InstallShield now lets you specify the folders where InstallShield should search for InstallShield prerequisite files (.prq files), their associated data files, and their dependencies. Previously, InstallShield searched for .prq files in the following location only: InstallShield Program Files Folder\SetupPrerequisites.

If you move any InstallShield prerequisites from the InstallShield Program Files Folder\SetupPrerequisites folder to a new custom location that you have defined on the Prerequisites tab of the Options dialog box (or any of the other places where search paths can be defined now), you may need to perform the following steps in InstallShield 2010 Express Edition or earlier projects when you upgrade them to InstallShield 2012 Spring Express Edition:

1. In the Redistributables view, clear the check box for each InstallShield prerequisite that is included in your project but is located in a custom location. Also clear the check box for each InstallShield prerequisite whose data files or dependencies were moved from the default location to a custom location.
2. Click the new Refresh button.
3. Select the check box for each InstallShield prerequisite that you removed from your project in step 1.

InstallShield removes the path of the prerequisite from the ISSetupPrerequisites table of your project. The full path was stored in this table in InstallShield 2010 Express Edition and earlier projects. Note that if you only clear a prerequisite's check box and then reselect it without clicking the Refresh button, InstallShield continues to use the full path, rather than just the file name, in the ISSetupPrerequisites table.

If you upgrade an InstallShield 2010 Express Edition or earlier project to InstallShield 2012 Spring Express Edition, change the location of an InstallShield prerequisite, and then add that prerequisite to your project, you do not need to perform the refresh procedure. Also, if you create a new project in InstallShield 2012 Spring Express Edition, you do not need to perform the refresh procedure. In both cases, InstallShield does not include the path in the ISSetupPrerequisites table of your project, which enables you to use the custom search path, instead of the default path.

See Also