How to make BackgroundWorker return an object?

In your DoWork event handler for the BackgroundWorker (which is where the background work takes place) there is an argument DoWorkEventArgs. This object has a public property object Result. When your worker has generated its result (in your case, a List), set e.

Result to that, and return.

In your DoWork event handler for the BackgroundWorker (which is where the background work takes place) there is an argument DoWorkEventArgs. This object has a public property object Result. When your worker has generated its result (in your case, a List), set e.

Result to that, and return. Now that your BackgroundWorker has completed its task, it triggers the RunWorkerCompleted event, which has a RunWorkerCompletedEventArgs object as an argument. RunWorkerCompletedEventArgs.

Result will contain the result from your BackgroundWorker. Example: private void bgw_DoWork(object sender, DoWorkEventArgs e) { int result = 2+2; e. Result = result; } private void bgw_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e) { MessageBox.

Show("Result received: " + e.Result.ToString()); }.

I'm assuming that you don't want to block and wait on RunWorkerAsync() for the results (if you did, there would be no reason to run async! If you want to be notified when the background process finishes, hook the RunWorkerCompleted Event. If you want to return some state, return it in the Result member of DoWork's event args.

EDIT: I posted prematurely -- finished my code example Example: private void BackgroundWorker_DoWork(object sender, DoWorkEventArgs e) { // do your thing .... // return results e. Results = theResultObject; } // now get your results private void BackgroundWorker_RunWorkerCompleted(object sender, RunWorkerCompletedEventArgs e) { MyResultObject result = (MyResultObject)e. Result; // proces your result... }.

Depending on your model, you either want to have your worker thread call back to its creator (or to some other process) when it's finished its work, or you have to poll the worker thread every so often to see if it's done and, if so, get the result. The idea of waiting for a worker thread to return its result undermines the benefits of multithreading.

RunWorkerAsync() starts the process asynchronously and will return and continue executing your code before the process actually completes. If you want to obtain the result of the BackgroundWorker, you'll need to create an instance variable to hold that value and check it once the BackgroundWorker completes. If you want to wait until the work is finished, then you don't need a BackgroundWorker.

You could have your thread raise an event with the object as an argument: ThreadFinishedEvent(this, new ThreadEventArgs(object)); where: public class ThreadEventArgs : EventArgs { public ThreadEventArgs(object object) { Object = object } public object Object { get; private set; } }.

Generally speaking when running a process async, The worker thread should call a delegate or fire an event (like ChrisF). You can check out the new PFX which has some concurrency function that can return values. For example there is a function called Parallel.ForEach() which has an overload that can return a value.

Check this out for more info msdn.microsoft.com/en-us/magazine/cc8173....

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.