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

Chapter 2: Getting Started
Upgrading from Earlier Versions of InstallShield
If you want to change the compression level or you do not want to use any compression, you can override
the default level through a machine-wide setting. For more information, see Configuring the
Compression Level for Files that Are Streamed into Setup.exe.
Previously, InstallShield did not include any support for compressing files that were streamed into the
Setup.exe file at build time. Thus, if you compare a release that was built in InstallShield 2008 Express
Edition or earlier with the same release that is built with the default compression level in InstallShield
2012 Express Edition, you may notice that the file size of Setup.exe is slightly different. In addition, the
time that is required to extract files may be slightly different.
Multi-Part .cab Files
InstallShield now has a default limit of 600 MB for each .cab file that it creates at build time for a
SingleImage release where all of the files are embedded in a single-file .msi package or a Setup.exe setup
launcher. When InstallShield is creating the .cab files for this type of release and it reaches this limit, it
splits the data into two or more .cab files, creating multi-part .cab files. This applies to new Express
projects as well as existing Express projects that are upgraded from InstallShield 2008 Express Edition
or earlier to InstallShield 2012 Express Edition.
You can modify the .cab size limit if necessary. In addition, if you do not want InstallShield to create
multi-part .cab files, you can configure it to create single .cab files. For more information, see
Configuring the Maximum Size for .cab Files.
Previously, InstallShield did not create multi-part .cab files, and there was no built-in limit for the .cab
file size.
Proxy Server Support
You may want to configure your installation to download certain files only if they are needed on the
target system. For example, the Windows Installer engine, the .NET Framework, and some InstallShield
prerequisites may already be present on some or most target systems. Instead of embedding these files
in your installation (which would increase your overall installation size), you can configure your project
so that only the ones that are needed are downloaded at run time.
If your end users access the Internet through a proxy server and your installation is configured to
download files, the installation now uses the system proxy settings that are manually configured in
Internet Explorer during the download. This occurs even if another browser on the target system is the
default browser.
Note that InstallShield does not include support for the Automatically Detect Settings functionality in
Internet Explorer. (If end users have the Automatically Detect Settings check box selected in Internet
Explorer for their LAN connection and the installation needs to download files, the installation fails
because the files cannot be downloaded. If it is possible that your end users may have the Automatically
Detect Settings check box selected in Internet Explorer for their LAN connections, you may want to
embed all of the files in your installation rather than configure them to be downloaded; if the files are
embedded, the failures can be avoided.) However, InstallShield does support the Automatic
Configuration Script functionality that is set up for LAN connections in Internet Explorer.
This is the behavior for all new projects in InstallShield 2009, as well as all projects that are created in
earlier versions and then upgraded to InstallShield 2009.
In InstallShield 2008 and earlier, the installation attempted to use the proxy server settings that were
configured in whatever browser was the default browser. However, this was not always possible, and it
caused some problems:
InstallShield 2012 Express Edition User Guide ISE-1800-UG01 93