Minor Upgrade Help

[Mike Finnerty]

Am working on a basic MSI project in IS Developer 7.04. I have most everything working except for the minor upgrade. Have followed the instructions found in the online help and have created a self extracting installation file with Package for the Web 4. Until I set the packager to copy the setup files rather than delete them after installation completes, the remove would execute but when the reinstall tried to do its thing, the MSI file would be gone. By copying the files to a folder, both steps work. However, the setup files are left behind and cause an overwrite prompt the next time the installation package is run.

Is there a way to have the setup files deleted only after the entire upgrade process is complete?

[Mike Finnerty]

quote:
--------------------------------------------------------------------------------
Originally posted by smcburney
After months of working on this and fooling around, and scouring the IS knowledge base and the community, I finally have been able to perform a successful minor upgrade with my standard project, AND have the same install be used for a new install.

Some of the secrets are NOT documented anywhere that I could find, so I'm posting them here! Much of this may apply to a basic project too.


1. Change your package code. I set Product Configuration to generate a new package code every time I build a release. (this one is obvious, and is documented)

2. Increment your product version number. (this one is obvious and documented)

3. For your release, set the MSI command line params to:
REINSTALLMODE=voums REINSTALL=ALL

4. Create a custom action to set the property REINSTALL to a value of {}

5. Create a custom action to set the property REINSTALLMODE to a value of {}

6. Go to the Sequences view. Under Installation/User Interface insert both custom actions after CostInitialize. Give both of them a condition of "Not Installed"

7. Under Installation/Execute insert both custom actions after CostInitialize. Give both of them a condition of "Not Installed"

8. When a minor upgrade occurs, your script will execute the OnResumeUIBefore event, and the OnResumeUIAfter event. You can add custom script to those.


My only hope is that this message will save someone else hours, days, weeks, or even months of headaches!

--------------------------------------------------------------------------------
The above was for a standard MSI project. Without having seen the above, I arrived at something almost identical for a basic MSI project. My modifications were as follows:

5. Create a custom action to set the property REINSTALLMODE to a value of "omus"

6. Go to the Sequences view. Under Installation/User Interface insert both custom actions before CostFinalize. Give both of them a condition of "Not Installed"

7. Under Installation/Execute insert both custom actions before CostFinalize. Give both of them a condition of "Not Installed"

8. Use the "/w" command line parameter when running setup.exe