Stuck on Patch vs Upgrade - Advanced Installer Community
Aeroclassics
Posts: 5
Joined: Fri Feb 27, 2015 4:34 am

Stuck on Patch vs Upgrade

The problem is I need to create an installer for a new installation of an application and a patch/upgrade for the same application. I use Jenkins for my CI which kicks off AI when a build is successful once for the full install and once for patch/upgrade. Using Jenkins, builds only take place when the source in SVN has changed. So my version numbers look like 1.5.2043.22 one time and then next time 1.5.2074.23.

So I am stuck on do I want a patch project or an upgrade project?

I have been building my full install package as a single exe which seems to be problematic if dealing with a patch installer. I have been trying to figure out an upgrade project without much success. Ideally it would be nice if AI could decide which files have changed and use those only, but I am perfectly happy to replace all the files on the target. It looks to me like an Upgrade requires that you uninstall the old version. Well even though I have placed every protection I can find on the registry from inside AI the registry still gets blown away. That means people have to register the product again. Not what I want.

How do I get where I need to be. Upgrade or Patch? I do not want to uninstall if not necessary, just drop the new on top of the old. If uninstall is necessary how do I protect the registry?


Thanks,
Doug
Attachments
AdVISESetup_Patch.aip
(90.58 KiB) Downloaded 309 times
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Stuck on Patch vs Upgrade

Hello Doug,

Usually you should build a patch only if there is a small difference between the two versions of your product. Also, please be aware that when creating patches there are several patch creation rules that must be fully accomplished.

If there are major difference in file size and feature and components organization in your installer projects, then it is recommended to create your update setups as major upgrades.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Aeroclassics
Posts: 5
Joined: Fri Feb 27, 2015 4:34 am

Re: Stuck on Patch vs Upgrade

Thanks, Daniel.
Generally they are not anything more than small change, bug fixes and maybe a small feature. Anything larger would be a new release which looks like the major upgrade you referenced in your post.

Mostly what I am trying to accomplish is as follows:
  • An installer for a blank system which includes possibly installing a new version of SQL Server Express, laying on certain prerequisites, using a custom action to set some permissions and fill the database with required values
    Create a simple installer that would update an existing installation on the same major revision, say 1.5 for bug fixes and maybe a small new feature
    An installation that would be used to upgrade an installation from a previous release to a new on where a new database engine will have to be installed plus a new database and copying the old data from the previous version of the database to the new
There is no magic here and is pretty standard stuff. Where I may be having some trouble is every time Jenkins starts a build of the installers, AI wants to change the product code. If I understand correctly you should not change the product code for a simple patch or update. Upgrades and releases yes. So how does one control this?

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

Re: Stuck on Patch vs Upgrade

Hello Doug,

Yes, you are correct. When you need to build a patch you should not change the ProductCode after changing the ProductVersion. If you are using our command line support to change the ProductVersion, then you should use the "-noprodcode" command line switch.

If you have any questions just let us know.

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

Return to “Building Installers”