Question

To be more specific:

We have a web service (written in .Net) which utilizes a large number of COM dlls for core business logic (written in VB6). Assume for now that these are sealed libraries.

Unfortunately, many of these COM libraries implement their own error handling or validation messages; if we pass in data which isn’t complete, or if another COM dependency is missing, they’ll display a dialog box. These dialog boxes are the problem…when running in IIS, these message boxes hang the request, waiting for the user to click ok to a box that can’t be seen.

Does anyone know a way to trap these UI calls (potentially it could be a form.show instead of a messagebox) on the .Net side, so we can throw an exception instead?

Answer 1

With the caveat that I haven’t done this personally, I believe the intercept and redirect you desire could be achieved through Win32 Hooks