![]() It almost seems there is a problem using 10 versions at this point, but that's absurd. ![]() 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. To see images of the Upgrade view settings, you can see my Flexera Software post here I've attached the 8x to 10 log and log from the 10.0.257 upgrade. 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. Notable differences are how the Const/Enum’s are handled, using the New-Variable scriptlet. This time, we’re looking at Powershell, which is mostly the same story as previous efforts with other scripting engines. 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. Getting Started with InstallShield Automation and PowerShell. A major upgrade acts like a first-time installation if an earlier version is not present. An example is updating version 1.2 of a product to 2.0. I thought I would look ahead and ensure a Major Upgrade in our new version family worked as expected. In a major upgrade, the product changes are large enough to merit changes to both the product version number and the product code, as well as the package code. 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. |