COM MessageBox in need of Closing

[Mike R.]

I am creating an application that utilizes a COM application. In certain circumstances, the COM app will create an inaccessible message box which will prevent the first application from working (a deadlock). How do you monitor the COM message loop and dismiss the messagebox when it occurs, using .NET C# from the first application

From http://www.developmentnow.com/g/36_2007_10_0_23_0/dotnet-languages-csharp.ht

Posted via DevelopmentNow.com Group
http://www.developmentnow.com

 

[Guest]

It sounds like the COM app was written for a user, and the only way arround
it may be to simulate a user with SendKeys(). You will probably need a code
to run listening for a window to be shown with the name of the messagebox and
send an "{ENTER}" or similar. If this COM app is launched as a separate
process, then killing the process may be more likely to succeed. SendKeys
often runs into issues if there is a user interacting while your code is
interacting.