problem

The cleanest way to acomplish this provided by the .net framework is the asynchronous method invocation. To use it you have to do the following. - wrap your lengthy operations in a method to be asynchronously invoked - create a delegate to call the method through, say LengthyMethodInvoker - implement a method, say, DoFinalTasks in the form to perform the tasks to be done when thread B is done - create an AsyncCallback delegate wrapping DoFinalTasks - call LengthyMethodInvoker.BeginInvoke, supplying the AsyncCallback delegate as a parameter DoFinalTasks will be called when the lengthy calculations are done. This may be C# specific because the BeginInvoke method is not derived from Delegate but is supplied by the compiler. You can also create events in the two threads and fire them but things can easily get messed up and multithreaded applications are so damn hard to debug. So, BeginInvoke is a fine solution

1 Reply

Know the answer? Post it — somebody with the same question will find it here.

S_Kiryazov22y ago
The cleanest way to acomplish this provided by the .net framework is the asynchronous method invocation. To use it you have to do the following. - wrap your lengthy operations in a method to be asynchronously invoked - create a delegate to call the method through, say LengthyMethodInvoker - implement a method, say, DoFinalTasks in the form to perform the tasks to be done when thread B is done - create an AsyncCallback delegate wrapping DoFinalTasks - call LengthyMethodInvoker.BeginInvoke, supplying the AsyncCallback delegate as a parameter DoFinalTasks will be called when the lengthy calculations are done. This may be C# specific because the BeginInvoke method is not derived from Delegate but is supplied by the compiler. You can also create events in the two threads and fire them but things can easily get messed up and multithreaded applications are so damn hard to debug. So, BeginInvoke is a fine solution