Re-merge a forked installshield installation

Taking over for another Release Engineer and am stuck....he was
uneducated and create a seperate full and upgrade version of our
install. How do I get back to a single install?

The Tool 1.0.msi

The Tool 1.1.msi
Package Code: same as 1.0, but shouldn't have been
Product Code: same as 1.0, correct
Upgrade COde: same as 1.0, correct

The Tool 1.1 Upgrade.msi
Package Code: unique
Product Code: unique
Upgrade COde: unique


- MSI file names contain versions
- I'm fairly sure I'm correct in thinking the previous Release
Engineer should NOT have forked and created a seperate "upgrade"
version of the application, but am unsure how to proceed.
- THe Installshield .ISM for The Tool 1.1.msi is gone.
- LAN deployment only.

How do I get back to a single MSI for 1.2 and beyond?
-The Tool.MSI (handling both new and upgrades) -- remove version from
filename
-Not sure how to handle the two different upgrade codes that exist for
my install base. Some users have 1.0 and 1.1 upgrade; whereas others
have 1.1

"Alex" <alexknelson@gmail.com> wrote in message
news:19290571-e2fc-4205-b44d-85d1d9acc062@r11g2000yqa.googlegroups.com...
> Taking over for another Release Engineer and am stuck....he was
> uneducated and create a seperate full and upgrade version of our
> install. How do I get back to a single install?
> The Tool 1.0.msi
> The Tool 1.1.msi
> Package Code: same as 1.0, but shouldn't have been
> Product Code: same as 1.0, correct
> Upgrade COde: same as 1.0, correct
> The Tool 1.1 Upgrade.msi
> Package Code: unique
> Product Code: unique
> Upgrade COde: unique
> - MSI file names contain versions
> - I'm fairly sure I'm correct in thinking the previous Release
> Engineer should NOT have forked and created a seperate "upgrade"
> version of the application, but am unsure how to proceed.
> - THe Installshield .ISM for The Tool 1.1.msi is gone.
> - LAN deployment only.
> How do I get back to a single MSI for 1.2 and beyond?
> -The Tool.MSI (handling both new and upgrades) -- remove version from
> filename
> -Not sure how to handle the two different upgrade codes that exist for
> my install base. Some users have 1.0 and 1.1 upgrade; whereas others
> have 1.1

The easiest way is to provide The Tool 1.2.msi which is a major upgrade to
all existing packages.
PackageCode unique
ProductCode unique
UpgradeCode same as 1.0

Include the UpgradeCode from The Tool 1.1 Upgrade.msi in your new MSI's
UpgradeTable [Make sure msidbUpgradeAttributesOnlyDetect bit is OFF in this
row]. In this way all previous packages will be treated as the "Old
version" and will force major ugprade [removal etc].

Do you need to support MSP creation? If so then just add another row to the
PCP TargetImages table to ensure that the resulting single MSP will apply to
all existing 1.0/1.1 MSI files.

Sincerely,
Adrian Accinelli