Upgrade Code is consistent and there is only one upgrade entry in the table for all of these scenarios. The max version field does not need to be set to Yes as each upgrade will target earlier versions. It almost seems there is a problem using 10 versions at this point, but that's absurd.Īny help in this would be greatly appreciated! On this new entry I tried including the MinVer, but to no avail. I even tried changing the Upgrade Code and creating a separate Upgrade table entry for the v10 family, but that didn't work either. You can download and see the install logs here. Here are images of the Upgrade settings in InstallShield. Changed the ProductCode and PackageCode and changed the MaxVersion field value in the Upgrade Table.Īll I see in the Log is Not Related and I don't see the ISFOUNDCURRENT property set in the second log. I can't for the life of me figure out what is wrong. When I try moving from 10.0.1 to 10.0.257, the old is not removed and I see two instances in Add Remove Programs. I thought I would look ahead and ensure a Major Upgrade in our new version family worked as expected. Old version detected and removed and the latest is put in place. When I run the upgrade from 8.6.x to 10.0.1 all works as planned. I'm working on our new product install which will the version 10.0 family.
0 Comments
Leave a Reply. |