Upgrade existing installation

[Avi]

Hi there,

I would like to get some more information regarding the upgrade option... (When changing the product version it ask you if you want to generate a new key for upgrades)

This is the workflow when generating new key, it is not seems to be right (to my opinion)

1. Generating new key
2. Upgrading existing installation
Now, the setup behavior is just like a clean install. It does not mention the upgrade, it lets you choose the installation directory and if you choose different location you will have your product installed twice but the existing shortcuts will point the new installation.
In the "add/remove" you will have now two entries, if you uninstall the new one the shortcuts will still point to the installation (which does not exist any more) etc…

In my point of view, when running the setup in upgrade mode, it should behave like this:
1. Ask you if you want a clean install or upgrade (clean install will force uninstall first)
2. If you choose upgrade, show you the license agreement and install it! No any other questions.
3. Add remove program will have only one entry, which will uninstall everything when needed.


Have I missed here something?
Avi

[Cata]

Dear Avi,

The Updates AI supports are Major Updates as per Windows Installer SDK. They work by completely completely uninstalling the existing product first, then installing the new one.

Two versions installed at once should not happen, if you answered "Yes" when asked about generating a new product code.

Patching an existing product is a different matter and it will be supported in the future.

Best regards,
Cata

[Avi]

Dear Cata,

Two versions are installed at once!

When generating a new product code, and choosing different installation directory. This include everything (Files, path, add/remove, etc...) and the common properties will be updated to the new installation.

Are you going to fix it?
When you are going to support patching to an existing installation?

Thanks,
Avi

[Cata]

Are you sure that
1) the "Automatically upgrade..." checkbox in the Install Parameters page is checked
2) a new, higher version was set for the newer product in the Product Details page
3) You answered Yes when asked to generate a new Product Version
4) The two install were made unde similar conditions (as Admin or Non-Admin)?

I tested it right now and I can't reproduce it.

The patches support should be ready by the end of the year.

Cata

[Edward-Ross]

I experience the same problem. If I create a new build id and run the install again I get a complete new install, including files and two entries in the software list from the windows control panel.

I did check the 'automatically upgrade...' setting. I did change the version number from '2.2.2 Release 2' to '2.2.2 Release 3', and I did say yes to the new product code.

[Avi]

It seems that the Windows installer ignore the furth field of the version in this case...

you should change one of the first 3 fields - the it will work nice.

example:
2.1.2.332 --> 2.1.3.355

[Edward-Ross]

Yes, you are right. Only up to the third sub-version is considered.

[csw]

Ok I eventually saw this post and realised that in order to avoid having to manually uninstall the existing package, I has to change the 3rd number and not just the 4th number.

I am a bear of very little brain, which probably explains why it took me so long (about 3 hours), but can I suggest an extra sentence to the dialog:

"The fourth field of the Product Version is ignored ... "

that pops up when you change the fourth number.

"... In order to create a package that automatically updates an older version and does not require a user to manually uninstall the package, you must modify one of the first three version numbers."

or words to that effect.

Great software by the way, thank you so much for creating a decent java installer at an affordable price!

C.

[Edward-Ross]

Is there any way to specify an new build number from the command line and then run the build? Or would you have to modify the xml and then run the build from the command line?

[Cata]

Not yet. That is actually on our todo list.

Changing the XML file directly is error prone, as you'd also have to generate a new Product Code.

Cata

[Guest]

I'm working on automating our build process - so being able to set the version number automatically from the command line is really important. Do you have any information on when this feature will be available?

Many thanks,

Ed.

[Cata]

This feature is available starting with 2.3 which will be released today or tomorrow.

Cata

[Edward-Ross]

Fantastic.

Thanks for providing such good customer support. I think your company's responsiveness keeps Advanced Installer ahead of the competition!

[mjvitale]

I understand that upgrading a product by means of the product code does an uninstall of the previous one and a fresh install of the new one.

But if my installation is big and I made some minor changes, I don't want the user to download the whole kit and kabuddle, and do a whole install again.

Isn't there some way to just update the modules that changed while incrementing the product code? And if so, how? Withing the same AIP file or a new one? If within the same file, do I simply remove all the files that haven't changed, and just add the one or 2 modules that did change?

[Cata]

Currently the only way to do this is by upgrading the whole product.

The next version, 2.6 due for release later this month, will provide support for Patches, which will allow minor updates of installed products.

Cata