Proper way to Dispose of a BackGroundWorker

by

BackgroundWorker derives from Component. Component implements the IDisposable interface. That in turn makes BackgroundWorker inherit the Dispose() method.

Deriving from Component is a convenience for Windows Forms programmers, they can drop a BGW from the toolbox onto a form. Components in general are somewhat likely to have something to dispose. The Windows Forms designer takes care of this automatically, look in the Designer.cs file for a Form for the “components” field. Its auto-generated Dispose() method calls the Dispose() method for all components.

However, BackgroundWorker doesn’t actually have any member that requires disposing. It doesn’t override Dispose(). Its base implementation, Component.Dispose(), only makes sure that the component is removed from the “components” collection. And raise the Disposed event. But doesn’t otherwise dispose anything.

Long story short: if you dropped a BGW on a form then everything is taken care of automatically, you don’t have to help. If you didn’t drop it on a form then it isn’t an element in a components collection and nothing needs to be done.

You don’t have to call Dispose().

More Related Contents:

  1. BackgroundWorker RunWorkerCompleted Event
  2. How to wait for a BackgroundWorker to cancel?
  3. Unhandled exceptions in BackgroundWorker
  4. Can you link to a good example of using BackgroundWorker without placing it on a form as a component?
  5. What’s wrong with using Thread.Abort()
  6. How to pass parameters to ThreadStart method in Thread?
  7. How to invoke a UI method from another thread
  8. The calling thread cannot access this object because a different thread owns it [duplicate]
  9. Updating an ObservableCollection in a separate thread
  10. Code for a simple thread pool in C# [closed]
  11. Unable to use more than one processor group for my threads in a C# app
  12. Why does this simple .NET console app have so many threads?
  13. A reproducible example of volatile usage
  14. thread with multiple parameters
  15. Event handlers not thread safe? [duplicate]
  16. Difference between lock(locker) and lock(variable_which_I_am_using)
  17. Looking for an example of a custom SynchronizationContext (Required for unit testing)
  18. What is the difference between ManualResetEvent and AutoResetEvent in .NET?
  19. Lock (Monitor) internal implementation in .NET
  20. .NET 4.0 and the dreaded OnUserPreferenceChanged Hang
  21. Advantage of using Thread.Start vs QueueUserWorkItem
  22. Reading an int that’s updated by Interlocked on other threads
  23. How to get awaitable Thread.Sleep?
  24. Thread parameters being changed
  25. Queue of async tasks with throttling which supports muti-threading
  26. ThreadStaticAttribute in ASP.NET
  27. Handling events from out-of-proc COM server in managed STA application
  28. Async and Await with For Loop [duplicate]
  29. Calling an async method from a synchronous method
  30. In WPF, what is the equivalent of Suspend/ResumeLayout() and BackgroundWorker() from Windows Forms

Leave a Comment