Can a nested msi custom action be placed in defferred execution
Can a nested msi custom action be placed in (Inscript option : deferred execution-user context/system context)...
since I getting error as "custom action specifies unsupported error type"
But when I use it in immediate mode.....custom action is executing fine...
Just wan to know whether it can be placed between IntallInitiallize and InstallFinalize in deffred mode
since I getting error as "custom action specifies unsupported error type"
But when I use it in immediate mode.....custom action is executing fine...
Just wan to know whether it can be placed between IntallInitiallize and InstallFinalize in deffred mode
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
pjgeutjens
13 years ago
No I don't think it can be, since at this point (deferred context) the main MSI will have 'locked' the use of the Windows Installer Engine for itself, and only one installation at a time can be active. So the nested MSI gets denied.
I'm not 100% sure though ( I avoid nested MSIs like the Bubonic plague), so maybe google can provide more detailed info.
PJ
I'm not 100% sure though ( I avoid nested MSIs like the Bubonic plague), so maybe google can provide more detailed info.
PJ
Posted by:
anonymous_9363
13 years ago
In a word, no. You can't run 2 installations simultaneously.
In any event, nested MSIs are The Work Of Satan and should be avoided. Either build a stub executable to run the installations in sequence or, better, use your deployment mechanism to do so.
In any event, nested MSIs are The Work Of Satan and should be avoided. Either build a stub executable to run the installations in sequence or, better, use your deployment mechanism to do so.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
