Using statement vs. IDisposable.Dispose()

by

using is basically the equivalent of:

try
{
  // code
}
finally
{
  obj.Dispose();
}

So it also has the benefit of calling Dispose() even if an unhandled exception is thrown in the code within the block.

More Related Contents:

  1. What is a NullReferenceException, and how do I fix it?
  2. What is the best workaround for the WCF client `using` block issue?
  3. Custom Compiler Warnings
  4. Nested using statements in C#
  5. Difference in months between two dates
  6. Way to have String.Replace only hit “whole words”
  7. When should I use “using” blocks in C#? [duplicate]
  8. When is a custom attribute’s constructor run?
  9. Capture screenshot Including Semitransparent windows in .NET
  10. How do I determine a mapped drive’s actual path?
  11. Get File Icon used by Shell
  12. How is performance affected by an unused using directive?
  13. How to find overlapping controls that I added to form?
  14. Inconsistency in divide-by-zero behavior between different value types
  15. Is String a primitive type?
  16. What is a predicate in c#? [duplicate]
  17. Difference between Lookup() and Dictionary(Of list())
  18. yield return statement inside a using() { } block Disposes before executing
  19. BinaryWriter Endian issue
  20. Questions about Entity Framework Context Lifetime
  21. .NET Configuration (app.config/web.config/settings.settings)
  22. How to Start a Process Unelevated
  23. Save Settings in VB.Net or C#
  24. .NET graph library around? [closed]
  25. center MessageBox in parent form [duplicate]
  26. using statement FileStream and / or StreamReader – Visual Studio 2012 Warnings
  27. What steps do I need to take to use WCF Callbacks?
  28. How to insert a Symbol (Pound, Euro, Copyright) into a Textbox
  29. Dynamically changing Textbox’s AutoComplete List causes AccessViolationException, any advice?
  30. As of today, what is the right way to work with COM objects? [duplicate]

Leave a Comment