How can I tell when a thread have finished when using a thread pool?

Since you are talking about UI, you might want to look at BackgroundWorker, which offers a RunWorkerCompleted event that fires on the UI thread and indicate success/failure/cancel etc.

Since you are talking about UI, you might want to look at BackgroundWorker, which offers a RunWorkerCompleted event that fires on the UI thread, and indicate success/failure/cancel etc. msdn.microsoft.com/en-us/library/system.... Personally, though, I'd just run a callback method at the end of my worker code (remembering to switch back to the UI thread, via Dispatcher. Invoke in WPF or this. Invoke in winforms).

1 The BackgroundWorker is a wrapper around the thread pool. It provides all the code he would have to write manually. Asynchronous Delegates also schedule work on the thread pool.In other words: don't use the ThreadPool directly.

Use an object that wraps the thread pool with useful extras, such as "complete" callbacks. – Ian Boyd Mar 19 at 14:43.

You can execute the methods in the thread itself (you have to take care of invoking yourself to access the gui thread): ThreadPool. QueueUserWorkItem(p => { check_news(validrsslist, 0); //do something after the task is finished }).

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.