Thanks again, Chris. I agree, having that async CA and the other CA communicating via RPC just for the log messages to way overkill. It'll probably be lesser work re-writing the entire UI.
My only concern is though, that I'll have to now look at bootstrapping .NET Fx, (earlier than expected) - and re-write all those UI dialogs in Winforms - where in reality I only want to add a couple of dialogs in Winforms to enhance the internal UI. (Because, the internal UI to select features etc, disk cost, change install dir etc are all quite nice, and easily done in Wix). So, other than this log message issue, do you think there are other problems with the Winforms + Internal UI mix approach (like the one I'm using)? Cheers Krishna chrpai wrote: > > Some people have suggested running an async CA prior to the dialog chain > and then using an RPC mechanism to pass messages to it for logging and > instructing it to shut down. > > Seems like overkill to me to get around an MSI limitation but if it's > really important to you, it can be done. Of course there is always > just dump MSI UI and use an external UI handler. > > -- View this message in context: http://www.nabble.com/Problem-with-DTF-Custom-action-invoked-via-PushButton-Event-%3A-DoAction-tp17719937p17726236.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
