Upgrade Issues - 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!

Stevo3000
Posts: 30
Joined: Fri Jan 23, 2009 12:00 pm

Upgrade Issues

Hi,

We have been building our installation projects with InstallAware but are currently in the process of moving over to use Advanced Installer. InstallAware uses two guids to refer to an MSI; the product id and the revision id. This allows up to release more then one installer with the same version (X.X.X) which will automatically update other versions as the revision id will be changed for each build. We need to be able to get the same functionality with Advanced Installer. Currently we just get a warning message telling us to un-install from add/Remove programs.

We also need to be able to Un-Install our existing installers from Advanced Installer, as mentioned above we have the product guid (this is constant for our product using InstallAware).

Cheers,
Steve Hipwell
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Upgrade Issues

Hi Steve,

I'm afraid that Advanced Installer does not support this (it uses the standard Windows Installer support). Basically, a new version of the package should have a different Product Code and a higher version. This is the way major upgrades work in Windows Installer. You can read more about this in the Upgrades page from the User Guide.
We also need to be able to Un-Install our existing installers from Advanced Installer, as mentioned above we have the product guid (this is constant for our product using InstallAware).
For this you can try using the "Upgrades" page. Basically, your package will use the Upgrade Code of the old version to automatically uninstall it when it runs.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Stevo3000
Posts: 30
Joined: Fri Jan 23, 2009 12:00 pm

Re: Upgrade Issues

Hi Cosmin,

This may be a deal breaker for us! Our software is released with major minor and build remaining constant for months at a time. The revision number is incremented for each indervidual build of our software. Our installers are released with the X.X version and this will stay the same for a large period of time.

I think I've found a work around by using the custom upgrade rules and removing the product version from the top auto generated rule. Then incrementing the version so a new product code is generated and then setting it back.

It is not a very scalable solution but it will have to do while we evaluate. Is there not a better solution available for people who don't want to use patches but who upgrade their installers frequently?
For this you can try using the "Upgrades" page. Basically, your package will use the Upgrade Code of the old version to automatically uninstall it when it runs.
Please could you explain this in more detail as the user guide is not very clear about the steps involved.

Cheers,
Steve Hipwell
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Upgrade Issues

Hi Steve,
Our software is released with major minor and build remaining constant for months at a time. The revision number is incremented for each indervidual build of our software. Our installers are released with the X.X version and this will stay the same for a large period of time.
Please note that Windows Installer uses three fields for the ProductVersion: major.minor.build. Therefore, your packages can keep the major and minor versions constant and when you want to release a new version you increase the build number.
Is there not a better solution available for people who don't want to use patches but who upgrade their installers frequently?
The best solution for updating an installation are patches. If you cannot use patches, it is recommended to use major upgrades. If you don't want to use major upgrades, you can try using small updates (this is more difficult for the user). I'm afraid that this is what Windows Installer supports.
Please could you explain this in more detail as the user guide is not very clear about the steps involved.
In the "Upgrades" page you can click on the "New" button and select an older version of your package. After that, the New Upgrade dialog is shown with details about the upgrade rules (you can click OK on this dialog). These steps will make Advanced Installer automatically add the Upgrade Code of the old package in the Upgrades list.

When your package runs, it will use this Upgrade Code to find older versions on the target machine. If it finds one, it will automatically uninstall it (if it can).

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Stevo3000
Posts: 30
Joined: Fri Jan 23, 2009 12:00 pm

Re: Upgrade Issues

Hi Cosmin,

Our installer uses x.x (although we have to use x.x.x with Active installer which isn't a major problem for us) but the software uses x.x.x.x so we cannon keep incrementing the installer version. My work around shows that the problem can be solved, it just leaves the possibility of error. What would be best would be for use to be able to chose to turn patching off and to be able to give a new id to each build of our software (even better if each build configuration had a seperate id).

I've tried to do the old version un-installing but I get an error. I don't think this is a bug in AI, I think it is more likely a bug with installAware. Do you know af any issues between the two systems?

Cheers,
Steve Hipwell
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Upgrade Issues

Hi Steve,
to be able to give a new id to each build of our software (even better if each build configuration had a seperate id).
I'm not sure I understand to what ID you are referring. Can you please give me more details about this? The identity of a MSI package is given by the following GUIDs:
- Product Code
- Package Code
- Upgrade Code

This identity is also defined by the Product Version.
I've tried to do the old version un-installing but I get an error.
Can you please give me more details about this? What is the exact error you are encountering?

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Stevo3000
Posts: 30
Joined: Fri Jan 23, 2009 12:00 pm

Re: Upgrade Issues

Hi Cosmin,

What would work best for us would be if there was a setting to make AI give a new Product Code to each build of the installer (even better if it could generate a new code for each build configuration). This would allow us to keep our installer version constant with our product version.

As far as the error we're getting trying to uninstall InstallAware installers; it looks like they are not preserving the contents of their installer as it's looking for files in the temp folder.

Cheers,
Steve Hipwell
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Upgrade Issues

Hi Steve,
What would work best for us would be if there was a setting to make AI give a new Product Code to each build of the installer (even better if it could generate a new code for each build configuration). This would allow us to keep our installer version constant with our product version.
I'm afraid that this is not supported by Advanced Installer or by Windows Installer. A new version of the product needs to have a different Product Code and a higher version in order to automatically upgrade older versions.
As far as the error we're getting trying to uninstall InstallAware installers; it looks like they are not preserving the contents of their installer as it's looking for files in the temp folder.
Since the error is shown by the package created with InstallAware, I'm not sure what the cause may be.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Stevo3000
Posts: 30
Joined: Fri Jan 23, 2009 12:00 pm

Re: Upgrade Issues

Hi Cosmin,
cosmin wrote:I'm afraid that this is not supported by Advanced Installer or by Windows Installer. A new version of the product needs to have a different Product Code and a higher version in order to automatically upgrade older versions.
I don't belive this is true! As I've already said (and there is altleast one other person on the forums doing this) that tricking AI into updating the product code by changing the version and then rolling the version back allows us to automatically upgrade older installers. What would be good was if there was a propper option to do this rather than having to trick AI!

Cheers,
Steve Hipwell
Cosmin
Posts: 5797
Joined: Tue Jul 10, 2007 6:39 pm
Contact: Website

Re: Upgrade Issues

Hi Steve,
I don't belive this is true! As I've already said (and there is altleast one other person on the forums doing this) that tricking AI into updating the product code by changing the version and then rolling the version back allows us to automatically upgrade older installers.
If you have two packages with the same Product Version and a different Product Code, the newer package will not automatically upgrade the older one. Although they may use the same installation folder, in the "Add or Remove Programs" applet in the Control Panel there will be two entries (one for each package). In order to use the second package to upgrade the first one you can try adding the first package in the "Upgrades" page of the second package.
What would be good was if there was a propper option to do this rather than having to trick AI!
Currently Advanced Installer does not support a direct way of changing the Product Code. However, this improvement is on our TODO list and it will be available in a future version.

Regards,
Cosmin
Cosmin Pirvu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
Stevo3000
Posts: 30
Joined: Fri Jan 23, 2009 12:00 pm

Re: Upgrade Issues

Hi Cosmin,
cosmin wrote:If you have two packages with the same Product Version and a different Product Code, the newer package will not automatically upgrade the older one. Although they may use the same installation folder, in the "Add or Remove Programs" applet in the Control Panel there will be two entries (one for each package). In order to use the second package to upgrade the first one you can try adding the first package in the "Upgrades" page of the second package.
This is not entirely true! If the upgrade rules are left alone this is the behaviour that is seen. But if you remove the version from the top auto generated rule (as I said in an earlier post) then changing the product code and keeping the same version will result in an auto upgrade.

Cheers,

Steve Hipwell

Return to “Common Problems”