Ok, thanx to kind people in here i now know the way to pass the INSTALLDIR to a deferred CA executing an VBS in the binary table. YEAH
So, now the question for convenience:
I need to start several deferred CAs that launch installed executables depending on installed features. Do i have to do the CustomActionData immediate CA for everyone of them, or does somebody know a more convenient way?
Maybe also a vbscript that holds the code to start all, and can enable/disable depending on the installation selected?
Thanx for every hint!
Cheers
Stefan
This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Mastering CA-Data part II
Started by
Stefan Secker
, Apr 22 2002 16:56
1 reply to this topic
Posted 22 April 2002 - 18:13
In the InstallExecute sequence, prior to InstallInitialize I have created an immediate CA with lots of MsiGetProperty calls and store the values of any properties I need in script global variables and then use them as I please without having to use the CustomActionData mechanism.
Not strictly Kosher, but still tidier considering the alternative.
Dave.
Not strictly Kosher, but still tidier considering the alternative.
Dave.