Please eliminate for me a purpose of Custom Action Type 135, 151, 183 and others named "Launch a second .msi package".
I receive this numbers with "Calculating the Custom Action Type" utility, provided in InstallShield X Professional documentation.
Furthermore, I can't find description for this numbers of Custom Action in Microsoft documentation. Numbers I find in docs: 7, 23, 39 – named “Nested Custom Actions”.
But it possible to add this type of action with Custom Action Wizard in InstallShield X IDE.
How it can be explained?
Perhaps, Custom Action Type utility misprints?
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.
Calculating the Custom Action Type utility misprin
Started by
AntonS
, Nov 23 2004 13:36
3 replies to this topic
Posted 24 November 2004 - 20:18
The customa ction type number is a combination of base type and several optional flag (scheduling, return processing etc) that add up to these numbers.
Stefan Krüger
InstallSite.org twitter facebook
Posted 26 November 2004 - 11:42
Thank you.
Do you see a enumeration of optional flags somewhere in docs?
I find only Custom Action Execution Scheduling Options in Platform SDK:
msidbCustomActionTypeFirstSequence 256
msidbCustomActionTypeOncePerProcess 512
msidbCustomActionTypeClientRepeat 768
Do you see a enumeration of optional flags somewhere in docs?
I find only Custom Action Execution Scheduling Options in Platform SDK:
msidbCustomActionTypeFirstSequence 256
msidbCustomActionTypeOncePerProcess 512
msidbCustomActionTypeClientRepeat 768
Posted 27 November 2004 - 18:08
You should also check the "Custom Action Return Processing Options"
Stefan Krüger
InstallSite.org twitter facebook