Hi all,

I have an InstallShield app that is called via a setup.exe which calls a Vendor msi.

There are lots of Custom Actions within this Vendor msi but the only ones I am interested in are 3 which call a dll which seems to install 3 other msi's stored with the source files.

The dll has differect functions in it that do various things and obviously one of those functions is to run my other msi's!

I have tried installing these seperately and have taken the Custom Actions out of the Sequence but for some reason when these other msi's are installed outside of the dll function call they don't install properly.

Is there any way I can find out what command line this dll is using to install the other 3 msi's?

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


Search for DebugView in the forum, it will do what your asking for.

hmmm think I have to post a howto for this as there's so many asking for such debugging ;)
Answered 09/06/2006 by: AngelD
Red Belt

Please log in to comment
I found debugview but when i ran my installation DebugView didn't pick anything up! Is there anything i need to do once DebugView is running?
Answered 09/07/2006 by: mark_holland21
Fourth Degree Green Belt

Please log in to comment
You need to create the REG_DWORD registry value HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer\Debug and set the data to 00000002 before running DebugView
Answered 09/07/2006 by: AngelD
Red Belt

Please log in to comment