How to produce AI-Updater configs for multiple builds correctly?

[burnersk]

I have an application setup with three builds (single MSI setup, Active Directory setup, web setup). The current build setup produces the following folder structure, which represent the online location (prefix https://example.com/downloads/).

• MyApplicationName\
  • 1.2.3.4\
    • MyApplicationName-1.2.3.4-Setup.msi
      (e.g.: https://example.com/downloads/MyApplicationName/1.2.3.4/MyApplicationName-1.2.3.4-Setup.msi)
    • Web\
      • MyApplicationName-1.2.3.4-Web-Setup.exe
      • MyApplicationName-1.2.3.4-Web-Setup.msi
      • [...].cab
    • Active-Directory\
      • MyApplicationName-1.2.3.4-Active-Directory-Setup.msi
      • [...].*

I want to place the updates.txt file(s) right under the application folder (e.g. https://example.com/downloads/MyApplicationName/updates.txt).

However, I got confused when I try to setup the AI-Updater project for the first time...
Do I have to make three different AI-Updater projects? How should I setup the AI-Updater project at all? Am I limited to one specific build (e.g. single MSI setup)?

[Daniel]

Hi,

Yes, please note that the updates configuration project is limited to a single build only. You cannot include into a single updates configuration project multiple builds of your setup product. Therefore you will have to create three updates configuration project, one for each build.

Then into you setup project create a property in "Properties" page that will have build specific values pointing to the specific build updates URL. This property you can set afterwards in the "Updates configuration file URL" field in the Updater page.

Have a look on our "How to deploy updates for various regions, channels or editions?" article that expose a similar setup project configuration.

If you have any questions or doubts do not hesitate to write us back.

All the best,
Daniel

[scotcro]

Well, this does not make sense to me. I think if you would support build variables in the Updater you could do this, using the per build setting from the main installer.

[Daniel]

Thank you for your feedback on this, but unfortunately this design is not supported by our updates configuration project.

Thank you for your understanding.

All the best,
Daniel