Installshield 2011 - Issue Updating Existing Software in Version 2009.727.1365 Format
Using Installshield 2011 we are creating major update and software update issues in this product version format - 2009.727.1365. We continue to receive the standard "Installed software is newer than the product to install" message. As of IS 2011, the major version has to be less than 255 from what I can compile, and I think the old format we are using breaks the check for update.
I created an IS test project with upgrade from 1.00.0000 to 2.00.0000 without any problems, so I think the problem must be related to the format of the already installed version of the product.
Is there a way to use InstallScript or something to compare our old format with the new one and then do an override?
Any help would be greatly appreciated. Thanks in advance!
** I ended up using Christopher in the link below (Exceeding version restrictions). This seems to do a pretty good job of uninstalling an existing product. Thanks again Guys!
source to share
The ProductVersion property is not valid. The SDK says:
The value of the ProductVersion property is the string version of the product. This property is REQUIRED.
The string format looks like this:
major.minor.build The first field is the major version and has a maximum value of 255. The second field is a minor version and has a maximum value of 255. The third field is called the build version or update version and has a maximum value of 65,535.
I also recommend reading Overriding Version Limitations .
There are hacks to get around this if you understand how FindRelatedProducts and RemoveExistingProducts work.
source to share
It sounds like you will need to remove or change the main-upgrade ISPreventDowngrade element that detects and prevents such a downgrade (which is usually what you want).
(Added question here also: http://community.flexerasoftware.com/showthread.php?t=195076 .)
source to share
Even if it's older, I would like to add my two cents. I am creating an Installshield 2012 Spring project and I had the same problem. Our previous installers had a product version in 2005.xx.xxxx format. Obviously this year 2005 was a problem.
Instead of setting the ISACTIONPROP1 property to any value (as stated in http://community.flexerasoftware.com/showthread.php?195076-Old-Product-version-in-2009-727-1365-format ). I added a main update element with the following values:
Legacy installers product code: xxx (enter here here) Minimum version: 2005.001.0001 Maximum version: 2005.255.65535 Inclusive version range (may be overflowed)
In this case, the system allows the format 2005.xxx.xxxx. He found and removed the previous installation. For our new installations, we will use our "normal" versions:
5.008.0001 5.009.0001 ...
source to share