Skip to main content

Difference Between Finalize and Dispose Method

 .Net Framework provides two methods Finalize and Dispose for releasing unmanaged resources like files, database connections, COM etc. This article helps you to understand the difference between Finalize and Dispose method.

Difference between Finalize & Dispose Method
Finalize
Dispose
Used to free unmanaged resources like files, database connections, COM etc. held by an object before that object is destroyed.
It is used to free unmanaged resources like files, database connections, COM etc. at any time.
Internally, it is called by Garbage Collector and cannot be called by user code.
Explicitly, it is called by user code and the class implementing dispose method must implement IDisposable interface.
It belongs to Object class.
It belongs to IDisposable interface.
Implement it when you have unmanaged resources in your code, and want to make sure that these resources are freed when the Garbage collection happens.
Implement this when you are writing a custom class that will be used by other users.
There is performance costs associated with Finalize method.
There is no performance costs associated with Dispose method.
For Example,
  1. // Implementing Finalize method
  2. public class MyClass
  3. {
  4. //At runtime C# destructor is automatically Converted to Finalize method.
  5. ~MyClass ()
  6. {
  7. //TO DO: clean up unmanaged objects
  8. }
  9. }
For Example,
  1. // Implementing Dispose method
  2. public class MyClass : IDisposable
  3. {
  4. private bool disposed = false;
  5.  
  6. //Implement IDisposable.
  7. public void Dispose()
  8. {
  9. Dispose(true);
  10. }
  11.  
  12. protected virtual void Dispose(bool disposing)
  13. {
  14. if (!disposed)
  15. {
  16. if (disposing)
  17. {
  18. //TO DO: clean up managed objects
  19. }
  20.  
  21. //TO DO: clean up unmanaged objects
  22.  
  23. disposed = true;
  24. }
  25. }
  26. }

Note

  1. You cannot override the Finalize method in the C# or C++ languages. But you can override Finalize method in VB.NET since it does not support destructor.
  2. You should not implement a Finalize method for managed objects, because the garbage collector cleans up managed resources automatically.
  3. A Dispose method should call the GC.SuppressFinalize() method for the object of a class which has destructor because it has already done the work to clean up the object, then it is not necessary for the garbage collector to call the object's Finalize method.
  1. // Using Dispose and Finalize method
  2. public class MyClass : IDisposable
  3. {
  4. private bool disposed = false;
  5.  
  6. //Implement IDisposable.
  7. public void Dispose()
  8. {
  9. Dispose(true);
  10. GC.SuppressFinalize(this);
  11. }
  12.  
  13. protected virtual void Dispose(bool disposing)
  14. {
  15. if (!disposed)
  16. {
  17. if (disposing)
  18. {
  19. // TO DO: clean up managed objects
  20. }
  21.  
  22. // TO DO: clean up unmanaged objects
  23.  
  24. disposed = true;
  25. }
  26. }
  27.  
  28. //At runtime C# destructor is automatically Converted to Finalize method
  29. ~MyClass()
  30. {
  31. Dispose(false);
  32. }
  33. }

Comments

Popular posts from this blog

Accessing File Stored in Windows Azure Blob Storage Using jQuery

Did you know it was possible to access the Windows Azure Blob Storage directly from JavaScript, for example using jQuery? At first, it sounds obvious, since Blobs are after all accessible from a public UR. But in practice, there is a very big hurdle: the Web browser’s Same Origine Policy or SOP, that restricts JavaScript code to accessing resources originating from the same site the script was loaded from. This means that you will never be able to load a Windows Azure Blob using XMLHttpRequest for example! Fortunately, there is a popular workaround called JSONP (“JSON with Padding”). The idea behind this technique is that the script tag is not submitted to the SOP: an HTML page can thus load a JavaScript file from any site. So, if you expose your data in an “executable” form in JavaScript, a page will be able to load this data using a script tag. For example: <script type=”text/javascript” src=”http://www.sandeepknarware.in/exemple.jsonp”> </script> But how can ...

Support for debugging lambda expressions with Visual Studio 2015

Anyone who uses LINQ (or lambdas in general) and the debugger will quickly discover the dreaded message “Expression cannot contain lambda expressions”. Lack of lambda support has been a limitation of the Visual Studio Debugger ever since Lambdas were added to C# and Visual Basic.  With visual studio 2015 Microsoft has added support for debugging lambda expressions. Let’s first look at an example, and then I’ll walk you through current limitations. Example To try this yourself, create a new C# Console app with this code: using System.Diagnostics; using System.Linq; class Program { static void Main() { float[] values = Enumerable.Range(0, 100).Select(i => (float)i / 10).ToArray(); Debugger.Break(); } } Then compile, start debugging, and add “values.Where(v => (int)v == 3).ToArray()” in the Watch window. You’ll be happy to see the same as what the screenshot above shows you. I am using Visual Studio 2015 Preview and it has some limitati...

gcAllowVeryLargeObjects Element

There are numerous new features coming with .NET 4.5 and here, on this blog, you can find several posts about it. But the feature we are goint to talk about today is very exciting, because we were waiting for it more than 10 years. Since .NET 1.0 the memory limit of .NET object is 2GB. This means you cannot for example create array which contains elements with more than 2GB in total. If try to create such array, you will get the OutOfMemoryException. Let’s see an example how to produce OutOfMemoryException. Before that Open Visual Studio 2012, and create C# Console Application, like picture below. First lets create simple struct with two double members like example below: 1 2 3 4 5 6 7 8 9 10 11 12 public struct ComplexNumber {      public double Re;      public double Im;      public ComplexNumber( double re, double im)      {    ...