Greetings all!

To your collective knowledge, is there a way to make Wise examine an MSI's files to determine which files SHOULD be in a merge module and then include those mergemodules in a package?

We actually have a situation where a vendor-supplied MSI places files into System32, and I know for a FACT these files are already in mergemodules.

We're thinking of just issolating these system files, but it seems more elegant to me to use mergemodules instead.

Any ideas?
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


The only way I know is with a Wise macro or an external vbscript.
Answered 05/13/2005 by: WiseUser
Fourth Degree Brown Belt

Please log in to comment
to my knowledge the only time Wise can examine the files in a package is when you are doing your setup capture. Wise spots files that are also available in Merge Modules at this stage. It prompts you at the end of the capture if you would like to include the MM's or leave the files in the package.
To set this facility up open Wise and go to Installer Editor. Go to Tools > Options > Merge Modules. here you must point to a folder that contains all the Merge Modules released by Wise, "c:\Wise Share Point\Merge Modules" should be specified.

In your vendor msi case i suggest that you compare the versions of the files you think should be in a MM to the file in the MM. if your MM is the same or higher then delete the files via the mst and add the MM.
i dont agree with editing a vendor msi in this regard though as you may lose vendor support.
Answered 05/16/2005 by: misk
Orange Senior Belt

Please log in to comment