/build/static/layout/Breadcrumb_cap_w.png

Wrapped msi's in Vendor msi - need to know command line used

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?

Cheers,
Rgds,
Mark

0 Comments   [ + ] Show comments

Answers (3)

Posted by: AngelD 18 years ago
Red Belt
0
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 ;)
Posted by: mark_holland21 18 years ago
Fourth Degree Green Belt
0
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?
Posted by: AngelD 18 years ago
Red Belt
0
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
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ