Hi, In general you cannot access/set any MSI properties in deffered custom action. Change the script execution to immediate and you can use MessageBox but this does not solve focus problem. We use other (a bit ugly method): to use the same action/function in two sequences we make action immediate and it sets some property if the error occurred, let say ERROR_OCCURED to the message that describes the error. In the button event we call that custom action and then immediately after it SpawnDialog conditioned to this property and this dialog shows this property. In Execute sequence we call custom action type 19 conditioned on error property immediately after our custom action. Thus we eliminate calling any messages from custom action because MsiProcessMessage does not work in dialogs on button event.
-- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Any-ideas-on-how-to-solve-MessageBox-focus-can-be-lost-using-Custom-Action-DLL-tp7584319p7584696.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Own the Future-Intel® Level Up Game Demo Contest 2013 Rise to greatness in Intel's independent game demo contest. Compete for recognition, cash, and the chance to get your game on Steam. $5K grand prize plus 10 genre and skill prizes. Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
