How can I do a Minor Upgrade

[Craig Daniel]

What I really want to do is what Microsoft refers to as a "Minor Upgrade". This is supposed to be an upgrade in which the Product Version number is changed, features and/or components can be added or updated, but the Product Code is not changed. I always thought that Windows Installer would handle this right from the MSI file and just "do the right thing" automagically. Based on what I've been reading in these forums, I must conclude that either this type of update is, in fact, not impossible, or else no installer tool actually supports it (including IA).

One might think that a patch could solve this problem, but after reading IA's docs and quite a few posts, I've determined that this is not true. Patches have two fundamental limitations that make them useless for me (and IMHO, seriously limit their usefulness in general): 1. They require previous installation media (unacceptable for our user base) and, for all practical purposes, won't work with compressed self-extracting EXE installers. 2. They cannot change the version number of installed products (effectively transforming it into the newer product).

So, it appears I have no alternative than to do a complete uninstall/reinstall cycle to accomplish something as simple as replacing a single file with a newer version, and updating the version number that appears in add/remove programs. IA gives me the flexibility to deal with this and to hide it from the user, but it still forces me (the developer) to do extra work on the script and more extra work to preserve state across the uninstall/reinstall cycle - work I would not have to do if I could just replace a couple files and be done with it.

If I've missed something here, I'd sure like to know about it. Thanks.

[CandiceJones]

You may use Persistent Variables to help with the state persistence issue.

With the patching route, you can patch against web builds. If you build a web build with a single offline web media block, it will not require access to installation sources at patch time, nor will it attempt to download anything from the web at either patch installation or initial installation. A web build with a single offline web media block is identical to a single file self extracting build, except it locally caches its sources (which is what you want in this scenario).

One of those two approaches would be the way to go in this case.

[SteveDude]

I believe the IA guys are doing exactly what you are wanting when you select generate license for the IA product. They are generating an installer just for you on their server and just then just updating a couple of files when it is downloaded and installed. They might be doing something as simple as just renaming a file on the server or as complex as using their automation object based on you customer information.

[Gizm0]

It's the second. Using the automation object based on customer information. That's the way actually to have your own company info stamp on the About screen of the installer.