Still one of the best who played the beautiful game. I see where you come from however ;)

I use WSS on a daily basis and it will be great if we have a forum for it. Thanks Emad

John, Whether humanity is destroying the planet or not is a bigger issue that I don't want to get into here. And it is definitely your choice whether to belong to this group or not. Regards Emad

John, In general, I agree with Chris Maunder's comment in the lounge. Also, I am not here to debate with you any specific subject. I just wanted to say that people wherever they are need to realize that they belong to one single identity. And that is humanity. There is enough trouble in the world. You are a lucky man you grew up where you did. Thanks for your consideration. Emad

yeah the application just quits...

Hi all, We are having an issue with a WinForm app disappearing with no warning when the user does some UI actions (clicking, dragging, etc.) on various windows and dialogs. There is no sequence of events that is known to reproduce the problem and we are handling 'unhandled exceptions' through a form. We have looked at memory usage, GDI objects, handles, stack overflows and none seem to be the cause as far as we can see. Any other reasons that could cause such a problem? Any help is greatly appreciated. Thanks very much Emad

hi Judah, yes it seems like it is a problem with the vendor's library. I am not sure about the cancel flag. We are working with Legacy code that we need to wrap the cancellation code around (not new design). Also, having code littered with checks like (if cancelled) doesn't seem to be the best solution for us. We are running the work on a background thread as you suggested. Leaving the work to run sounds like a good idea. It is worth a try if all fails. Thanks for your help.

We are using a COM library through interop (ESRI's lib). Since the library is sometimes slow we decided to create a dialog to allow the user to cancel a long running request. The request is running on a thread. Pressing the cancel button on that dialog will Thread.Abort() the request. The problem we are facing is that the application's behavior is unpredictable after the user performs several cancellations. Sometimes, the application waits forever (hangs) and sometimes it just takes all of the processor's time. As you can see there is little info here. The only thing that we know about the COM library is that it is running in a single threaded apartment - STA. Questions: 1. Is it possible to do this kind of threading work with an STA COM library through interop? 2. Is there any other way to do the same thing (other than aborting the thread)? 3. Do you have any experience with multi-threading ESRI tasks in .NET (not C++)? If yes, can you please provide any advice on how to tackle this problem. We posted this problem on ESRI's forums to no avail :confused: Any help is greatly appreciated. Thanks