Hi All,

I just got a question:
Does anybody know how to repair an installed msi with another msi.

I have a application named [application x 1.0], the application uses middleware [oracle client 9.2]. But there are more application that uses [oracle client 9.2]
so i don't want to use merge modules, that isn't usefull when you need to edit the installation and repackage the [oracle client 9.2].

What I'll is that when I startup [application x 1.0] and the middleware [oracle client 9.2] is damaged only then it is self repairing and then startup [application x 1.0]. Otherwise only starts [application x 1.0]

With kind regards,
Mark Aarden
0 Comments   [ + ] Show Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.


I put middleware such as Oracle Client as a separate prerequisite application and deal with it as a separate entity.

A trick for doing a self-repair check on something that doesn't launch through a shortcut or file association is to put a dummy .exe file in the application that does nothing; executes and immediately ends. Make it a key component in the root feature. To self-repair check the app, launch the dummy exe. If a key component is broken it will be fixed, if it's fine the dummy .exe will just terminate.
Answered 03/10/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
Answer this question or Comment on this question for clarity