1) When you invoke a CA through a dialog control event, the messages you attempt to write to the log don't end up in the log. You can work around this for debugging by using MessageBox or OutputDebugString to write out logging information.
2) When you invoke a CA through a dialog control event, and the CA sets properties, the dialog processing logic in the MSI runtime doesn't realize you've changed properties and it doesn't re-evaluate subsequent event conditions using the new property value. You can work around this by inserting a phony event that sets the property to its value, i.e. Foo = [Foo]. -- "The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download <http://legalizeadulthood.wordpress.com/the-direct3d-graphics-pipeline/> Legalize Adulthood! <http://legalizeadulthood.wordpress.com> ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ WiX-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wix-users
