Updates configuration files - 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!

mentalmushroom
Posts: 63
Joined: Wed Feb 08, 2012 8:08 am

Updates configuration files

Hello. I am a little bit confused by the way I should use updates configuration file. Periodically I release new versions of the product I develop, should I add all updates to the same updates configuration file? This takes too much HDD space to keep all the old installers on the disk, so I usually delete them (they are stored on the server only), but I noticed this way I can't build the updates configuration file when I need to release an update. Is there any solution for that?
No milk today
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Updates configuration files

Hello,

The update configuration project should be updated along with new updates. The update configuration file generated from that project should be replaced on your server and will tell the auto updater how the user will see your updates. This is detailed in Updates Configuration Projects user guide article.

You can get more insight on how to use the updater by following our Using The Auto Updater tutorial and subarticles.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
mentalmushroom
Posts: 63
Joined: Wed Feb 08, 2012 8:08 am

Re: Updates configuration files

Yes, I was following that guide, but I still was not sure whether I should update the same configuration file all the time. But how about my second question: I keep all the released versions on the server, so they are still visible for updater, but I don't want to store them on my HDD - they are not needed and simply take space. Is there any way to tell the update configuration project that it should just add new entries for the new update without replacing old ones or any other way to update the configuration file without having all the old versions on the disk?
No milk today
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Updates configuration files

Hello,
Is there any way to tell the update configuration project that it should just add new entries for the new update without replacing old ones or any other way to update the configuration file without having all the old versions on the disk?
Keeping backups of the update configuration project or its generated update configuration files is not needed. Keeping backups of previous project versions is however a recommended strategy in case something goes wrong.

All the best,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
mentalmushroom
Posts: 63
Joined: Wed Feb 08, 2012 8:08 am

Re: Updates configuration files

But without keeping all the previous installers (that were used for updates) I can't build the update configuration project. I keep all those packages, but I store them on the server, not on my machine.
No milk today

Return to “Common Problems”