Creating a better BackgroundWorker: CancelImmediately and other goodies

This blog has moved to http://osherove.com/blog
Published Wednesday, November 09, 2005 1:06 PM by RoyOsherove
Filed under:

Comments

Wednesday, November 09, 2005 3:57 PM by Oskar Austegard

# re: Creating a better BackgroundWorker: CancelImmediately and other goodies

I'm still stuck in 1.1 - so: from what you could tell, is the final BackgroundWorker component any different from the one Juval created?

One of the challenges involved with using the BWC is the non-typed nature of the e.Argument. I ended up writing a CodeSmith template to bundle my method parameters into a class to simplify the process...
Wednesday, November 09, 2005 5:40 PM by Roy Osherove

# re: Creating a better BackgroundWorker: CancelImmediately and other goodies

Oskar: The final component is not exactly the same but it works the same as the one in 1.1. The one Juval wrote was based in design on the final one that was released in 2005.
The final one employs .NET 2.0 specific classes such as AsyncOperation to do its bidding which was not possible in 1.1.

They could have used generics to help with the untyped natire of the e argument, but they somehow chose not to...
Wednesday, November 09, 2005 6:40 PM by Oskar Austegard

# re: Creating a better BackgroundWorker: CancelImmediately and other goodies

But the interface is the same? Method/Event names, etc?
Thursday, November 10, 2005 5:25 AM by Roy Osherove

# re: Creating a better BackgroundWorker: CancelImmediately and other goodies

yes. The same
Monday, December 05, 2005 1:15 PM by Denise Phillips

# re: Creating a better BackgroundWorker: CancelImmediately and other goodies

Do you have any unit testing examples working with these classes?
Friday, July 21, 2006 6:43 PM by Earl Damron

# re: Creating a better BackgroundWorker: CancelImmediately and other goodies

I think I am misunderstanding something. :-) I was hoping the BackgroundWorkerEx.StopImmediately would stop immediately, but it doesn't. This code always fails: if (bwEx.IsBusy) { Debug.WriteLine("Calling StopImmediately()"); bwEx.StopImmediately(); Debug.WriteLine("StopImmediately() returned"); } bwEx.RunWorkerAsync(loadState); Despite getting both messages in the immediate window, I still get a InvalidOperationException("BackgroundWorker_WorkerAlreadyRunning") when I call bwEx.RunWorkerAsync(...). Do I misunderstand what this component is for or how to use it? Thanks
Friday, July 21, 2006 7:37 PM by RoyOsherove

# re: Creating a better BackgroundWorker: CancelImmediately and other goodies

Calling them immediately one after the other may produce this problem due to a resource locking problem.

Calling thread.sleep(1) inside the "RunWorkerAsync" method as the first line shoudl solve it..

Thursday, February 08, 2007 12:55 PM by Bill Dieter

# re: Creating a better BackgroundWorker: CancelImmediately and other goodies

I read an article that says calling abort on a thread is a bad thing...

<a href="http://www.albahari.com/threading/part3.html></a>

I was hoping to use this in a database query tool, I wanted users to be able to cancel long running queries. I read somewhere else that calling abort on the thread doesn't cancel the operation on the server, it just means that the client thread is gone....and sometimes the server can't find the client and does wonky things like getting stuck in an infinite loop.

Is this safe to use to cancel long running queries against a database, and having the database cancel the query itself, rather than just having the client disconnect?

Saturday, February 06, 2010 7:30 AM by Extend the BackgroundWorker Control htt… « .NET Professional Programming

# Extend the BackgroundWorker Control htt&#8230; &laquo; .NET Professional Programming

Pingback from  Extend the BackgroundWorker Control  htt&#8230; &laquo;  .NET Professional Programming