Releases the managed resources in c#

Ken H

Hello friend,

How to determine whether the object is recovered?

class Program{

static void Main(string[] args){

Student student = null;

using (student = new Student())
{
Console.WriteLine("student is null:{0}\n",student == null);

}

Console.WriteLine("student is null:{0}\n",student == null);

}

}

public class Student : IDisposable
{

public Student() { }

~Student()
{
Console.WriteLine("Start Execute Destructor...\n");
}

public void Dispose(){

Console.WriteLine("Start Execute Dispose...\n");

}

}

Thanks.

4 Replies

Know the answer? Post it — somebody with the same question will find it here.

Vulpes11y ago
Accepted answer
There's nothing magical about the Dispose() method and it only does what you code into it.

So to release managed resources you'd set the corresponding fields to null. The GC will then clean them up in due course.

However, this will happen anyway when the object as a whole is garbage collected and so Dispose() is normally limited to cleaning up unmanaged resources (file handles, database connections etc.). The GC knows nothing about these and it's usually not enough to just garbage collect the managed wrapper - you need to specifically release the unmanaged resource to avoid a resource leak.
Ken H11y ago
Thank for you. :)
Ken H11y ago
I want to know is: How to Dispose releases the managed code, for example, a custom class.
Vulpes11y ago
If you want to check whether a custom object which implements IDisposable has been disposed or not, then you have to write your own property to tell you this. There is no way to tell otherwise as variables which refer to that object are not automatically set to null.

However, if you do this, then you can also check in the destructor whether the object has already been disposed and, if it hasn't, call Dispose() before you execute the rest of the destructor code, if any. This is a useful precaution in case you (or your users) forget to call Dispose() yourself:

using System;

class Program
{
static void Main(string[] args)
{
Student student = null;

using (student = new Student())
{
Console.WriteLine("student is null : {0}\n",student == null);
}

Console.WriteLine("student is disposed : {0}\n", student.IsDisposed);
}
}

public class Student : IDisposable
{
public bool IsDisposed { get; private set; }

public Student() { }

~Student()
{
if(!IsDisposed) Dispose();

Console.WriteLine("Start Execute Destructor...\n");

}

public void Dispose()
{
Console.WriteLine("Start Execute Dispose...\n");
IsDisposed = true;
}
}

The output is:

student is null : False

Start Execute Dispose...

student is disposed : True

Start Execute Destructor...

Incidentally, there is not usually much point in releasing managed resources as these will be cleaned up automatically by the GC in any case. The main purpose of the IDispose pattern is to clean up unmanaged resources as the GC knows nothing about these.