Why would a class implement IDisposable explicitly instead of implicitly?

by

This is normally done if the class has a Close method that is the exact same as Dispose. The original Dispose is hidden in an explicit implementation so that the exact same method doesn’t have two names.

It’s officially recommended here:

Do implement a Close method for cleanup purposes if such terminology is standard, for example as with a file or socket. When doing so, it is recommended that you make the Close implementation identical to Dispose…

Consider implementing interface members explicitly to hide a member and add an equivalent member with a better name.

Occasionally a domain-specific name is more appropriate than Dispose. For example, a file encapsulation might want to use the method name Close. In this case, implement Dispose privately and create a public Close method that calls Dispose.

(P.S. I disagree with this convention.)

More Related Contents:

  1. Proper use of the IDisposable interface
  2. Use of Finalize/Dispose method in C#
  3. Do HttpClient and HttpClientHandler have to be disposed between requests?
  4. Should I call Close() or Dispose() for stream objects?
  5. Using statement vs. IDisposable.Dispose()
  6. How do you reconcile IDisposable and IoC?
  7. Should you implement IDisposable.Dispose() so that it never throws?
  8. Dispose, when is it called?
  9. How do I dispose my filestream when implementing a file download in ASP.NET?
  10. Async network operations never finish
  11. returning in the middle of a using block
  12. What happens if i return before the end of using statement? Will the dispose be called?
  13. yield return statement inside a using() { } block Disposes before executing
  14. Questions about Entity Framework Context Lifetime
  15. Should IDisposable.Dispose() be made safe to call multiple times?
  16. Is IDisposable.Dispose() called automatically? [duplicate]
  17. Implementing IDisposable on a subclass when the parent also implements IDisposable
  18. Is it possible to force the use of “using” for disposable classes?
  19. What does Process.Dispose() actually do?
  20. What is IDisposable for?
  21. When should I use GC.SuppressFinalize()?
  22. Duck typing in the C# compiler
  23. Who should call Dispose on IDisposable objects when passed into another object?
  24. What is the difference between using and await using? And how can I decide which one to use?
  25. Manually destroy C# objects
  26. When or if to Dispose HttpResponseMessage when calling ReadAsStreamAsync?
  27. Guidelines For Dispose() and Ninject
  28. Do I need to Dispose a SemaphoreSlim?
  29. Who Disposes of an IDisposable public property?
  30. Determining if IDisposable should extend an interface or be implemented on a class implementing said interface

Leave a Comment