Updates

[anja_laenge]

Hello,

I need to create updates that meet the following requirements:
- it must not be designed as web update, instead the user should do the download himself
- the update setup should only contain changed files
- the update setup must not do an uninstallation of the previous version
- the upgrade must not ask for an installation path, it should determine the path of the already installed version
- the control panels list of installed programs must show the new version number

All requirements except the last one would lead to a patch installation but these must have identical version numbers.
What would be the best way to accomplish this?

Regards

[FrancescoT]

Dear Anja,

using MSI engine the only option that (partially) fits your requirements, it's to deploy a patch.
You may eventually use a custom Variable to keep track of the patch version and this may be stored in a custom key under the system registry.
Successively from your application, you may query such custom registry-key to acquire the installed version.

I do the same when I need to work with Patches, but of course, the package version listed under "Add Remove Program" will be not updated.

The above approach it's easy to implement ... but I don't know if it meets your needs as well.

Regards