Question

Possible Duplicate:
Calling null on a class vs Dispose()

Just want some information regarding Disposing an Object.

I have create a Employee Class which i inherit from IDISPOSIBLE Interface. Below is the sample Code

public class Employee : IDisposable 
 {
      private Int32 _RunID;

      public Int32 RunID { get { return _RunID; } set { _RunID = value; } }

        public void Dispose()
        {
            //Dispose(true);
        }
 }

Now my Question is, it a Good Coding Practice to Dispose every class we create and implementing/Inheriting it with IDisposible Interface even i have seen many other people code they directly set ObjEmployee = null; so just got confused which is good setting NULL or Implementing it With IDisposible Interface or None Of the Above ?

Answer 1

It depends, do you have managed resources (File handles, sockets, connections, etc….) that need to be gotten rid of along with your object? If yes then you need a Dispose() if your class contains basic types or just information you do not need to dispose and setting to null will give a hint to the GC to clear that memory.