I have a custom action that when called as a check in the InstallUISequence
writes data to the log file via session.Log stmts. But when a different method
in the same custom action is called from a dialog then none of the session.log
stmts are written to the log.
Here is how the custom action is called during the InstallUISequence:
<InstallUISequence>
<Custom Action="checkFoo"
After="CostFinalize"
Overridable="yes"/>
</InstallUISequence>
This is how the custom action is called from the dialog:
<Publish Event="DoAction" Value="checkFooBar"></Publish>
I'm baffled as to why this is happening. The only thing I can see different is
from looking at how the custom action is invoked in the log.
When called from the InstallUISequence the log says this: Calling custom
action CustomActions!Install.CustomActions.CustomActions
When called from the dialog event the log says this: MSI (c) (6C:48)
[10:00:03:869]: Invoking remote custom action. DLL:
Am I missing something to enable the sesion logging in all situations? Perhaps
there is some parameter that I need to set on the CustomAction declaration that
is being called from the dialog that would allow session.Log to succeed?
Thanks for any assistance.
Jack Alford
Hexagon Metrology
19 Interpro Drive, Building 24B-103
Huntsville, AL 35824
USA
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
WiX-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wix-users
