Loading
Re-merge a forked 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

 

 

Thanks for any guidance you can provide.

  • 0_M Urman (Flexera Software)

    The best option at this point is to create a major upgrade - go to the upgrades view and add a major upgrade item for each upgrade code. Note that changing the name of the MSI also requires you to use major upgrades (as opposed to minor upgrades).

Loading
Re-merge a forked installation