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

Chapter 2: Getting Started
Upgrading from Earlier Versions of InstallShield
Default Condition for the SetARPINSTALLLOCATION Custom Action
By default, all new Express projects contain the built-in InstallShield custom action
SetARPINSTALLLOCATION. This custom action, which sets the value of the
ARPINSTALLLOCATION property to the fully qualified path for the product’s primary folder, is
scheduled for the Installation Execute sequence, and it has no condition. In InstallShield 2008 Express
Edition and earlier, the default condition for this custom action was Not Installed. With this default Not
Installed condition, the custom action is not run during maintenance mode, and this results in a blank
value for the ARPINSTALLLOCATION property.
Upgrading Projects from InstallShield 12 Express Edition or
Earlier
The following information describes changes that may affect projects that are upgraded from
InstallShield 12 Express Edition or earlier to InstallShield 2012 Express Edition.
Upgrading Projects Created in Earlier Versions of InstallShield Express Edition
If you use InstallShield 2012 Express Edition to open a project that was created with an earlier version,
InstallShield 2012 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 .765 before converting it. Delete the .765 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 Express Edition projects in earlier versions of InstallShield
Express Edition.
You can migrate projects that were created with the following versions of InstallShield Express Edition
to InstallShield 2012 Express Edition: 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 migrated to InstallShield 2012 Express Edition.
End of Support for Windows 9x, Windows NT 4, and Windows Me on Target
Systems
InstallShield no longer supports the creation of installations for Windows 9x, Windows NT 4, and
Windows Me systems. If end users have one of these operating systems on their computer and they try to
run an installation that was built with InstallShield 2012 Express Edition, unexpected results may occur.
COM Extraction
When you use InstallShield to extract COM information from a COM server, InstallShield now puts the
data in the Registry table, instead of in the TypeLib table. Microsoft strongly advises against using the
TypeLib table, as described in the TypeLib Table topic on the MSDN Web site.
Unused Directories Automatically Removed from the .msi File at Build Time by
Default
Note that if you upgrade an Express project that was created in InstallShield 12 Express Edition or
earlier to InstallShield 2012 Express Edition, the new Keep Unused Directories setting on the Build tab
in the Releases view is set to No. Therefore, if a directory that is listed in the Directory column of the
Directory table is not referenced in any known location in the .msi file, InstallShield removes it from
the Directory table of the .msi file that it creates at build time. This occurs after any merge modules are
96 ISE-1800-UG01 InstallShield 2012 Express Edition User Guide