Determining if IDisposable should extend an interface or be implemented on a class implementing said interface

by

If you expect callers to only be able to interact with the interface, and never the implementation, then you want to have the interface extend IDisposable. If not, they’ll need to check if the value is IDisposable anyway to see if it needs to be disposed.

If the object responsible for disposing of the object knows of the concrete implementation, and it is only ever objects that are given references to it (but aren’t responsible for disposing of it) that use the interface, then consider the second option.

A good example of the first option is IEnumerator. Many IEnumerator objects don’t need to do anything when they’re disposed, but some do, and so the interface extends IDisposable because the object responsible for the creation/lifecycle of that object will (or should) never have knowledge of the underlying implementation.

An example of the second would be something like IComparer many objects that need to be compared are disposable, but the sections of code using an object through the interface aren’t responsible for it’s creation/lifecycle, so it needs no knowledge of whether or not that type is disposable.

More Related Contents:

  1. Dispose, when is it called?
  2. returning in the middle of a using block
  3. What happens if i return before the end of using statement? Will the dispose be called?
  4. Is it possible to force the use of “using” for disposable classes?
  5. What is IDisposable for?
  6. Do I need to Dispose a SemaphoreSlim?
  7. Who Disposes of an IDisposable public property?
  8. Proper use of the IDisposable interface
  9. Use of Finalize/Dispose method in C#
  10. Finalize vs Dispose
  11. Is it considered acceptable to not call Dispose() on a TPL Task object?
  12. Should I call Close() or Dispose() for stream objects?
  13. What is the difference between using IDisposable vs a destructor in C#?
  14. Disposing WPF User Controls
  15. Using statement vs. IDisposable.Dispose()
  16. Should you implement IDisposable.Dispose() so that it never throws?
  17. How do I dispose my filestream when implementing a file download in ASP.NET?
  18. Async network operations never finish
  19. Does garbage collector call Dispose()? [duplicate]
  20. yield return statement inside a using() { } block Disposes before executing
  21. Questions about Entity Framework Context Lifetime
  22. Should IDisposable.Dispose() be made safe to call multiple times?
  23. Is IDisposable.Dispose() called automatically? [duplicate]
  24. Why Dispose is not called even with using-statement?
  25. What happens if I don’t call Dispose on the pen object?
  26. Should I always disconnect event handlers in the Dispose method?
  27. When or if to Dispose HttpResponseMessage when calling ReadAsStreamAsync?
  28. using statement FileStream and / or StreamReader – Visual Studio 2012 Warnings
  29. What’s the purpose of GC.SuppressFinalize(this) in Dispose() method?
  30. Datatable.Dispose() will make it remove from memory?

Leave a Comment