C#

System.Threading.Thread mythread = new System.Threading.Thread
     (delegate()
           {
               try
               {
                    throw new Exception("Oh no, my thread crashed!");
               }
               catch(Exception err)
               {
                    File.WriteAllText(Environment.GetFolderPath(Environment.SpecialFolder.Desktop) + @"\error.log",
                         DateTime.Now.ToString() + Environment.NewLine + err.ToString() + Environment.NewLine + Environment.NewLine);
               }
           });
   mythread.Start();

George_George wrote:

BeginInvoke and EndInvoke will be defined automatically for every delegate, right?

George_George wrote:

just looks like for every class we defined, toString, GetHashCode, etc. are defined automatically?)

George_George wrote:

What are the pros and cons compared with the pattern of using EndInvoke to wait for result and the pattern of using WaitHandle to wait for result. To my points, I think they function the same

Spacix One wrote:

Must remember the other execution is stuff not within the thread that the waitone was called on or other processes running on the system.

N a v a n e e t h wrote:

But WaitHandle.WaitOne() allows you to do some processing before EndInvoke() is called

George_George wrote:

I think EndInvoke can achieve the same effect, e.g. you can do something and then invoke EndInvoke.

George_George wrote:

we can call EndInvoke even if after the asynchronous method completes to retrieve results, right

George_George wrote:

N a v a n e e t h,

S. Senthil Kumar wrote:

1. Any exceptions that occurred in the asynchronous method will be thrown when you call EndInvoke, so if you don't call it, you'll miss those.

George_George wrote:

From the link you referred, I can not find words like

George_George wrote:

If yes, I think the asynchronous method should be executed in another CLR thread, other than the current thread. Right?

George_George wrote:

And if any exception occurs in the CLR thread, could be caught in the current thread? I doubt it. Since I think the C# exception handling approach does not allow us to have cross-threads exception handling -- means exception occurs in one thread, and we can catch it in another thread? Any comments?

S. Senthil Kumar wrote:

Any exceptions that occurred in the asynchronous method will be caught by the .NET framework and will be rethrown in the thread that calls EndInvoke. So yes, the framework does have the ability to handle exceptions across threads.

George_George wrote:

In normal case of multi-threaded programming in C#, the exception thrown from one thread can not be caught from another thread, right?