[Bug 8243] Feature: Add MsiBreak to aid debugging custom actions

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=8243

------- Additional Comments From [e-mail]  2007-02-06 07:46 -------
Hello,

good to see that part committed ...
While debugging custom action code it seems the Windows MSI evaluates the
MsiBreak env variable against the action name as stored in msi tables, not the
custom dll function name "target" (some oversight from me, though it seemed more
useful).

Please fix the evaluation to use "action" msi_custom_action_info member instead
of "target" to make it feature compatible with Windows MSI server.

Regards