Updates configuration questions - Advanced Installer Community
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Updates configuration questions

Hi,
I have questions about the (.aiu) text file that is produced by my "updates config" project.

1) there seems to be a "ReleaseDate" entry that is possible. But I just published a file with ReleaseDate of 28/02/2015 (tomorrow) and yet when the updater.exe encouters this file today (02/27/2015 -NOTE the US style date format here) it says that their is a release. Can the ReleaseDate entry be used in the way that I'm thinking? That is a way to publish a file today, but only make it be downloadable after a certain date?

2) I named the text file that is produced by an "updates config" project as: AutoUpdateLatestVersion.aiu
But I have just seen instances where the downloaded file is called AutoUpdateLatestV.aiu. So, the question is, is there an inherent character limit constraint on what this .aiu text file should called.

Thanks.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Updates configuration questions

Hello,
1) there seems to be a "ReleaseDate" entry that is possible. But I just published a file with ReleaseDate of 28/02/2015 (tomorrow) and yet when the updater.exe encouters this file today (02/27/2015 -NOTE the US style date format here) it says that their is a release. Can the ReleaseDate entry be used in the way that I'm thinking? That is a way to publish a file today, but only make it be downloadable after a certain date?
No, I'm afraid this is not possible. The release date can be used only when you want to perform a license validation check when the Updater is launched. It is useful only if your license validation script also does a license expiration check. For example, if the current user license expiration date is earlier than the updates release date, than the Updater will deny the updates installation. For more details please take a look on our "Updater License Check" article.
2) I named the text file that is produced by an "updates config" project as: AutoUpdateLatestVersion.aiu
But I have just seen instances where the downloaded file is called AutoUpdateLatestV.aiu. So, the question is, is there an inherent character limit constraint on what this .aiu text file should called.
No, there is no limitation regarding how you should name the updates configuration file.

If you have any questions just let us know.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: Updates configuration questions

Thanks for the replies.

The weird thing about 1) that I saw yesterday is that in another scenario the file downloaded was called AutoUpdateLatest.aiu. This was never a problem before, so I will have to see if it continues, but just thought you should be aware that it's not consistent in what it trims from the file name.
kjullion
Posts: 176
Joined: Mon Nov 11, 2013 9:02 pm

Re: Updates configuration questions

Here is a different but slightly related question.

How do I support a client that would like to have a "staging" URL for their updater process. In other words, we do a release that is not public initially to a client that then does their own regression testing on our release. Then, when their regression is complete, and they give us the go ahead to make the release public. In that instance we would copy the system from the "staging" url to the "prodcution" url. But it seems that in the case of AI these URLs are tightly integrated not just to the .AIU file but to the Setup EXE itself. So, does that mean I have to do a Rebuild of the Setup so that the download URL gets switched from "staging" to "production"? Can this sort of task be automated, so that it's less susceptible to human error (typing in the URL or even copying and pasting)?

Is there any "scripting" that can be done generally with the Build process of AI? For instance with MSBuild you can specify the .SLN file and some parameters such as Release vs Debug. It would be nice we were possible to script AI so that you can have it do a Rebuild and change one or two elements within that build.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Updates configuration questions

Hello Kevin,
But it seems that in the case of AI these URLs are tightly integrated not just to the .AIU file but to the Setup EXE itself. So, does that mean I have to do a Rebuild of the Setup so that the download URL gets switched from "staging" to "production"? Can this sort of task be automated, so that it's less susceptible to human error (typing in the URL or even copying and pasting)?
Yes, this is true. When switching from staging to production you should trigger a rebuild of the installation project and set the production URL of your updates configuration file in the "Updater page -> Updates Configuration File URL field". To automate this task you can use the formatted reference of an installer property (e.g. [URL_PROP]) in the above field and, then when need to rebuild the production installer you can use the "Set Property" command to set the above property to the production URL before rebuilding the project.

For example, you can use a script like this to rebuild your project:

Code: Select all

AdvancedInstaller.com /edit MyProject.aip /SetProperty URL_PROP="<URL_Path>"
AdvancedInstaller.com /rebuild MyProject.aip
Is there any "scripting" that can be done generally with the Build process of AI? For instance with MSBuild you can specify the .SLN file and some parameters such as Release vs Debug. It would be nice we were possible to script AI so that you can have it do a Rebuild and change one or two elements within that build.
Yes, for this you can use our CLI support.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”