Using IDisposable all the times is good?

Question

I want to know suppose I create an object and then use (IDisposable(object)).Dispose() after using that object.

Will this help me to improve my performance?Or should I wait for GarbageCollector to collect that object?

http://msdn.microsoft.com/en-us/library/b1yfkh5e%28v=vs.110%29.aspx — Dennis, Mar 11 '14 at 07:23
http://stackoverflow.com/questions/538060/proper-use-of-the-idisposable-interface — SebastianStehle, Mar 11 '14 at 07:23

score 1 · Accepted Answer · answered Mar 11 '14 at 07:25

The primary use of this interface is to release unmanaged resources. The garbage collector automatically releases the memory allocated to a managed object when that object is no longer used. However, it is not possible to predict when garbage collection will occur. Furthermore, the garbage collector has no knowledge of unmanaged resources such as window handles, or open files and streams. Use the Dispose method of this interface to explicitly release unmanaged resources in conjunction with the garbage collector. The consumer of an object can call this method when the object is no longer needed

ref: http://msdn.microsoft.com/en-us/library/system.idisposable(v=vs.110).aspx

A more detailed description http://www.codeproject.com/Articles/413887/Understanding-and-Implementing-IDisposable-Interfa

The primary use of `IDisposable` is to release **resources**, no matter what nature those resources have. — Dennis, Mar 11 '14 at 08:14

score 0 · Answer 2 · answered Mar 11 '14 at 07:24

Its purely depends on the context which we used, for example objects like DB connection objects usually needs to be disposed, any stream related operations needs to be disposed. It's not necessary to dispose every object which we create, most of them are handled by GC.

Using IDisposable all the times is good?

2 Answers2