Updater configuration file - Advanced Installer Community

We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

yishai
Posts: 54
Joined: Wed Nov 23, 2005 11:54 pm

Updater configuration file

Hi

Let’s say I have customers with v1.0 and 2.0. I have just made a new release 3.0, and found a problem.

I have built a new version 3.1. I also created a patch v3.1 to upgrade from 3.0 to 3.1.

I want people who upgrade from 1 or 2 ( there might be also 1.1, 1.2, who knows, so it is for anything less than 3.0) to get the full 3.1. Those who upgrade from 3.0 should get the patch 3.1.

How would the auto update configuration file look like in this case?

[I know there is the Updates Configuration project. However, I have a fully automated system that needs to build multiple projects. i.e. I can not tweak it by hand, so either I can programmatic ally set the project it via a command line to do what I need or build the configuration file myself]

Thanks

-Yishai
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Updater configuration file

Hi,

The update from version 1 or 2 to version 3.1 represents a major upgrade and it can be done by using the automated upgrade feature. Basically, it requires a full installation package for the 3.1 version. This package should have the same UpgradeCode as versions 1 and 2, but it should have different Product Codes and versions.

The update from version 3.0 to 3.1 can be done with a patch. However, the patch cannot update versions 1 and 2. Therefore, a good solution is to distribute the full 3.1 package as an update (without using a patch).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
yishai
Posts: 54
Joined: Wed Nov 23, 2005 11:54 pm

Re: Updater configuration file

Thanks. I know this is the case, but this solution basically makes patches useless, as at any given moment i'll have users with an old version that needs an update and a new version that need only the patch.

I was looking (if it is possible) for the syntax that is supported by the auto updater.

[The goal is that when the autoupdater hits the aiu file it has an entry for 3.0 (i.e. minor update) and not 3.0 (i.e. major update)


Something like that (but I can't find the right syntax):

Code: Select all

;aiu;

// the first entry is used for v 3.0 (patch update)

[Versio_3.1]
Name = MyEditor 3.1
URL = http://www.myeditor.com/download/patch31.msi
Size = 23788
Description = This is a patch to the latest version
Feature = fix few bugs 
BugFix = bug 1
FilePath = %ProgramFiles%\MyEditor\xyz.exe
Version = 3.0

// the second entry is used for all pre v 3.0 (major update)

[Versio_3.1]
Name = MyEditor 3.1
URL = http://www.myeditor.com/download/fullinstall31.msi
Size = 3023788
Description = This is a full install to the latest version
Feature = major upgrade 
BugFix = Fix many bugs
FilePath = %ProgramFiles%\MyEditor\xyz.exe
Version = 2.0   <--    or meybe (Version <> 3.0) or Version = general
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Updater configuration file

Hi,

Please note that the names of the sections used in the Updates Configuration file should be unique. Therefore, instead of [Versio_3.1], you should use [Versio_3.1_patch] and [Versio_3.1_major].

Unfortunately, the Updater does not support what you are trying to do. Each update uses a detection criteria for detecting if its installed or not on the target machine. Since both the patch and the major upgrade update the main EXE of the application to the 3.1 version (for example), both updates will use the same detection criteria.

A solution for this would be to use a major upgrade which updates versions 1 and 2 to 3.0 and the patch which updates the version 3.0 to 3.1. Also, the patch would depend on the major upgrade.

I have added on our TODO list an improvement which will allow you to specify the target versions for each update. Thank you for your suggestion.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”