How to eliminate Unhandled Exception dialog produced by 3rd party application?

You could write a wrapper application that calls the 3rd party application directly and launch your application using Process.Start.

You could write a wrapper application that calls the 3rd party application directly and launch your application using Process.Start. Then in your wrapper application trap the exception so the users won't see the error message.

It's doable but you provide too little information :) – Lex Li Mar 23 '10 at 3:16.

This is of course illegal etc. But if the company has actually gone bankrupt then no one is there to pursue it.It is reasonable for you to support the code if you have no other choice. Reflector might give you a clue as to why the code crashes as well, perhaps you need to do something or call it with a parameter to stop it from doing so?

Next time don't try to use something without source code :) A workaround is to follow Chris' suggestion. A wrapper application can make use of such code, blog.jtbworld.com/2007/06/windows-live-w... Find the old application executable. Execute it in an AppDomain object created in the wrapper application.

Bind your application unhandled exception handler to this AppDomain object's UnhandledException event. msdn.microsoft.com/en-us/library/system.....

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.