InstallShield 2012 Spring Express Edition User Guide

Chapter 2: Getting Started
Upgrading from Earlier Versions of InstallShield
3. Create a back-up copy of the Settings.xml, in case you later need to revert to the original version.
4. Use a text editor or XML file editor to open the Settings.xml file.
5. Search for the element. It looks something like this:
6. Do one of the following:
• To specify the maximum size for .cab files, type the size in MB as the value of the default
attribute. In the aforementioned example, the maximum size is 600. The value should be 2048
or less, since the maximum size of a .cab file is 2 GB (2048 MB).
The default value is 600.
• If you do not want InstallShield to create multi-part .cab files, set the value of the default
attribute to -1.
7. Save the Settings.xml file.
8. Ensure that your XML code is well formed; if it is not well formed, you may have problems using
InstallShield. In most cases, you can identify improperly formed XML code by opening the
Settings.xml file in Internet Explorer. You should be able to expand and contract the major
elements of the file; if you cannot, check the code for errors.
Whenever you build a compressed SingleImage release for one of the applicable project types,
InstallShield creates the .cab files according to the requirement that you configured in the Settings.xml
file. Depending on the value that you specified in the Settings.xml file, the Media table of the .msi
package lists one or more .cab files.
Upgrading from Earlier Versions of InstallShield
If you have setup projects created with earlier versions of InstallShield or InstallShield Express, you can
open those projects with your new version of InstallShield. Because of the underlying technical
differences between earlier versions and InstallShield 2012 Spring Express Edition, the migration
process does not always produce a one-to-one correlation between what was in your old project and
what makes it into the new project. For example, InstallShield objects, which existed in earlier versions
of InstallShield Express, have since been replaced by merge modules. In some cases, what may have
been two objects in your old project could be replaced by a single merge module in your new project.
To learn more about migrating from earlier versions of InstallShield, see this section of the
documentation.
Upgrading Projects from InstallShield 2012 Express Edition
or Earlier
The following information describes possible upgrade issues that may occur when you upgrade projects
that were created with InstallShield 2012 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
2012 Express Edition or earlier to InstallShield 2012 Spring Express Edition.
InstallShield 2012 Spring Express Edition User Guide ISE-1900-UG00 85