InstallShield 2012 Spring Express Edition User Guide

Updating Applications
17
Installing upgrades for applications is a much more common operation than installing the original
release of an application. This makes creating effective, reliable upgrades a very important task.
“Updating Applications” provides solid background information on the different types of upgrades and
also clears up common misconceptions about patching. It helps you determine the best upgrade solution
for your product and guides you through the steps of creating upgrades and patches. In addition, this
section explains how you can use FlexNet Connect to notify end users that a new version of your product
is ready for release.
Upgrades Overview
The cost of maintaining software applications is often more expensive than the cost of original
development. This makes creating effective, reliable upgrades an important task. Being able to distribute
robust upgrades for an application depends on how the original installation package was structured and
distributed.
Windows Installer provides different methods for implementing three different upgrade types: small
update, minor upgrade, and major upgrade. Upgrades can be packaged as either a full installation or a
patch. A patch is simply another mechanism for implementing a type of upgrade. With a patch, however,
you deliver to your customers only the bits required to change an installed file into a new file, unlike a
full release.
Major Upgrades
Project: This information applies to Express projects.
InstallShield 2012 Spring Express Edition User Guide ISE-1900-UG00 319