 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
.NET Forum / Languages / C# / March 2008Background worker
Hello, Can you please tell me if I should use the background worker in the following way: if (worker.IsBusy) worker.CancelAsync(); (or I can avoid this if)? And in case I want to restart the background worker ,should I do it this way? worker.RunWorkerAsync(); Thank u ! Regards the "if(worker.IsBusy)", I imagine that yes, you can drop the if and just call CancelAsync. I say this because if you *had* to test IsBusy, you'd already have a race-condition (since the other thread could complete between the IsBusy and CancelAsync calls). However, including this test doesn't do much harm. Regards restarting, that sounds about right - but in this case you *do* want to check that it isn't already running since it throws an exception if you try to use it twice at once. There is no race condition here since it can only become "safer" (if you see what I mean). Mar You can "restart" the background worker by calling RunWorkerAsync, but you won't be able to call that until after you receive the RunWorkerCompleted event. Until you get that event you'll get an InvalidOperationException.  SignatureBrowse http://connect.microsoft.com/VisualStudio/feedback/ and vote. http://www.peterRitchie.com/blog/ Microsoft MVP, Visual Developer - Visual C# > Hello, > Can you please tell me if I should use the background worker in the [quoted text clipped - 9 lines] > > *** Sent via Developersdex http://www.developersdex.com *** A question: ThreadPool also provides the async execution of tasks. So when should I use ThreadPool and when BackgroundWorker? What's the difference between them? > A question: > > ThreadPool also provides the async execution of tasks. So when should > I use ThreadPool and when BackgroundWorker? What's the difference > between them? BackgroundWorker uses the ThreadPool. It adds to that the ability to deal with cross-thread issues, by providing an event-driven model for using it. In particular, the notification events like ProgressChanged and RunWorkerCompleted will be raised on the same thread that created the BackgroundWorker instance. This means you can use the BackgroundWorker class from a Form instance, creating it on the main GUI thread for the Form and not having to worry about using Invoke() or BeginInvoke() to call code that accesses the Form instance itself. If your background thread code needs to communicate with a GUI object like a Form- or Control-derived class, then the BackgroundWorker class provides a nice simplified API to do that. Pete i use background worker quite abit, and never use CancelAsync In my case each thread must complete..whether successful or a error occurred , they complete if your case is long running threads and you have a UI I would set a cancel property in the class doing the work to cancel the job that it is doing.. therefore the worker thread always complets > Hello, > Can you please tell me if I should use the background worker in the [quoted text clipped - 9 lines] > > *** Sent via Developersdex http://www.developersdex.com ***
Free MagazinesGet these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...
|
Reply to this Message
|
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.