Best practice for updates/upgrades/patches - Advanced Installer Community
JNeck
Posts: 1
Joined: Thu Aug 26, 2010 5:44 pm

Best practice for updates/upgrades/patches

Hello,

we are new to AdvancedInstaller and are looking for best practices to work with updates/upgrades/patches.

One basic thing that we don't fully understand is if we have to create a new project for every update we need to build or if we have the same project file every time and only make changes to it. Is the procedure the same for updates and patches?

Is there any guide or white paper for best upgrade practices?

Thanks in advance,
Jens
mihai.petcu
Posts: 3860
Joined: Thu Aug 05, 2010 8:01 am

Re: Best practice for updates/upgrades/patches

Hello Jens,

A best practice for managing your upgrades would be to make changes, increase the Product Version and save the new version with a new name ( Save as ... -> new name preferably including your Product Version ).
Keep your upgrade projects organised on your hard drive. This way you will have a complete history of your upgrades and it will help you later on if you encounter problems or need a backup.

Please note that after each Product Version increase, you will be prompted to change the Product Code as well. You only need to change the Product Code when you are about to create an upgrade and not while creating a patch.
If you change the Product Code, you won't be able to create a patch project.

Follow our "Using The Updater" tutorial. It will guide you step by step to deploying and understanding the Advanced Installer Updater feature.

Regards,
Mihai
Mihai Petcu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
hadas
Posts: 43
Joined: Mon Jan 06, 2014 10:53 am

Re: Best practice for updates/upgrades/patches

Hello,

Can the same project be Installer and Upgrade (if it finds OLDPRODUCT)? Since the actions are the same in every upgrade, I want to create one file, and only change the product version, should I change the upgrade code version?

My product contain files, create services, has a DB and configuration directory (configuration is based on user inputs). The Upgrade should use the configuration folder (User shouldn't see the configuration dialogs again), remove the services and re-install them, crate a backup for the DB and run DB upgrade.

I'm not sure what will be the best practice to achieve that.
I'v configure the aip to uninstall prev version and then install the new one. Regrading this configuration, should I, for example, mark the remove services as "replaced by a new version" , and the create services as "upgrade"?
When every step is being execute?



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

Re: Best practice for updates/upgrades/patches

Hello Hadas,
Can the same project be Installer and Upgrade (if it finds OLDPRODUCT)? Since the actions are the same in every upgrade, I want to create one file, and only change the product version, should I change the upgrade code version?
In order to create a major upgrade installation package you should proceed like this:
- create a backup copy of your current project (.aip) and keep it on a location from your computer (this is a best practice for having a full history of your setup projects and easily check the settings changes between different versions of your projects)
- open the .aip (project file) and follow the steps debated in our "Automatically upgrade older product versions" article section
I'v configure the aip to uninstall prev version and then install the new one. Regrading this configuration, should I, for example, mark the remove services as "replaced by a new version" , and the create services as "upgrade"?
When every step is being execute?
I'm afraid I don't fully understand what you mean. Can you give us more details about this (maybe exemplify)?

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

Return to “Common Problems”