destructor and dispose
-
I read "Many times many articles", But still I am struggling to know the exact difference. Apart from this if I say Object=nothing. What is the impact on Garbage Collector, I want what exactly the garbage collector will take care of this.
-
I read "Many times many articles", But still I am struggling to know the exact difference. Apart from this if I say Object=nothing. What is the impact on Garbage Collector, I want what exactly the garbage collector will take care of this.
The short answer is that when you set
Object=nothing(orObject=nullin C#) nothing happens until the garbage collector runs. When the garbage collector runs is non-determinisitic which means that it can't really be predicted. For more details the following from MSDN should help. MSDN wrote: During a collection, the garbage collector will not free an object if it finds one or more references to the object in managed code. However, the garbage collector does not recognize references to an object from unmanaged code, and might free objects that are being used exclusively in unmanaged code unless explicitly prevented from doing so. The KeepAlive method provides a mechanism that prevents the garbage collector from collecting objects that are still in use in unmanaged code. Other than managed memory allocations, implementations of the garbage collector do not maintain information about resources held by an object, such as file handles or database connections. When a type uses unmanaged resources that must be released before instances of the type are reclaimed, the type can implement a finalizer. In most cases, finalizers are implemented by overriding the Object.Finalize method; however, types written in C# or C++ implement destructors, which compilers turn into an override of Object.Finalize. In most cases, if an object has a finalizer, the garbage collector calls it prior to freeing the object. However, the garbage collector is not required to call finalizers in all situations. Also, the garbage collector is not required to use a specific thread to finalize objects, or guarantee the order in which finalizers are called for objects that reference each other but are otherwise available for garbage collection. In scenarios where resources must be released at a specific time, classes can implement the IDisposable interface, which contains the IDisposable.Dispose method that performs resource management and cleanup tasks. Classes that implement Dispose must specify, as part of their class contract, if and when class consumers call the method to clean up the object. The garbage collector does not, by default, call the Dispose method; however, implementations of the Dispose method can call methods in the GC class to customize the finalization behavior of the garbage collector. --Colin Mackay--