Advice on Updates - 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!

dudedolf
Posts: 14
Joined: Mon Aug 10, 2009 5:18 pm

Advice on Updates

Hi,

I am very happy with the product and have now purchased it. However, i am would like to know what the best procedure for doing updates are.

I understand (i think) the following.

- Create an application ver 1.0
- Add the file and folders
- To make and update, make a copy of 1.0 (as a form of backup) and change the version number to 1.1
- Allow AI to create the new version and a Product Code

The questions i have are.
- Do i need to keep the same files and folders in the 1.1 aip file, or just have the updated files in there?
- If i install version 1.0 on a PC but am now on 1.2 how will the updated be queued so that version 1.1 is applied and then 1.2?
- Would the updates URL be different for each updated version?

I would like to have some grounding before i embark on this part of the installer

Thanks
Rudy
Bogdan
Posts: 2796
Joined: Tue Jul 07, 2009 7:34 am
Contact: Website

Re: Advice on Updates

Hi,
Do i need to keep the same files and folders in the 1.1 aip file, or just have the updated files in there?
If you will distribute the package as a MSI you can modify everything you wish to. If the package is being distributed using a patch you must keep the previous files and also respect some other rules. Here are the rules.
If i install version 1.0 on a PC but am now on 1.2 how will the updated be queued so that version 1.1 is applied and then 1.2?
Usually when an update is being build, for example version 1.2, it is based on the previous version , that is version 1.1. So updates from version 1.1 should be a part of version 1.2.

However if you are referring to a patch authoring for version 1.1 and 1.2 here is what you should do. In the patch project you can add as Upgraded both update version 1.1 and 1.2. This way the last patch will contain both of the updates.
Would the updates URL be different for each updated version?
No, the updates URL should remain the same for all the updates. This is the path from where the updater.exe will download the updates configuration file.

An upgrade can be done either using a major upgrade or a patch. Both of them can be distributed using the auto-updater. Here is a tutorial that may help you.

Regards,
Bogdan
Bogdan Mitrache - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
dudedolf
Posts: 14
Joined: Mon Aug 10, 2009 5:18 pm

Re: Advice on Updates

Thanks for the swift reply.

My main concern is that we use an SQL Database and sometimes we may do updates which we only want to run once.

E.g.

Ver 1.0 is inital version
Ver 1.1 is a file update
Ver 1.1.1 is an SQL Update which we only wish to run once
Ver 1.2 is a file update and SQL update separate from 1.1.1

What i would like is that on a new deployment, which is started at V 1.0 that all the files updates are run so that the application to brought up to date.

Thanks and hope this makes sense
Rudy
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Advice on Updates

Hi Rudy,

A major upgrade automatically uninstalls the previous version before installing the new one. This means that everything installed by an old version is completely replaced by a newer version. So your latest version should contain all the updates you want to make.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
MindTooth
Posts: 37
Joined: Mon Aug 17, 2009 12:40 am

Re: Advice on Updates

Personally I prefer that you always create the project that it replaces all the old files.

Birger :)

Return to “Common Problems”