How to call destructor in C # XNA

I have a object and simply want to de开发者_如何学Gostroy it on some event. How to call the destructor in XNA?

---

Set the object to null and the Garbage Collector will pick it up on it's next run.

As a side note, if the object is something that you create often (enemies, bullets etc..), then you may want to use a pool instead of deleting the object. This would mean that object is recycled, and thus, the garbage collector is called less often which will increase performance.

---

While your mileage may vary, my preference is to use IDisposable and Dispose() of objects I no longer need. This is esp. true when you are using unmanaged resources, but having the Dispose() set up declares intent.

See this resource on GC.SuppressFinalize for a good example of how to implement IDisposable.

http://msdn.microsoft.com/en-us/library/system.gc.suppressfinalize.aspx

---

Set reference to this object to null.

---

After setting the object to null, if you want for some reason the object to be collected immediately, call GC.Collect().

---

What kind of object? If is an Disposable/IDisposable you should call object.Dispose() Otherwise, you can just use object=null, and it will be 'cleaned' automatically. This is not C you're working in ;)

If your 'object' is actually a complex class or something with more objects in it, you might want to consider making it an IDisposable class.

---

If the object holds any unmanaged resources then implement IDisposable (and use using or call Dispose() on it when you're done with it).

If it doesn't hold unmanaged resources then the garbage collector will claim it "at some point" when there are no more references to it.

GC.Collect() will make the garbage collector collect and it will "destroy" your object if there are no references to it. This is not a very good idea since it has performance implications (it takes time and promotes other objects into a higher generation making them last longer in memory before being reclaimed).

Why do you need the object destroyed at a certain fixed time?

---

What you want to do is call GC.SuppressFinalize() if you are handling the cleanup yourself... Usually you use GC.SuppressFinalize() within an IDisposable class. See this code example for the common use of IDisposable:

http://msdn.microsoft.com/en-us/library/system.gc.suppressfinalize.aspx

If you really need to have it Garbage Collected right away:

var myObj = new MyObject();

// This object will be cleaned up by the Dispose method.
// Therefore, you should call GC.SupressFinalize to
// take this object off the finalization queue 
// and prevent finalization code for this object
// from executing a second time.
GC.SuppressFinalize(myObj);

But I caution you that you should really let the object go out of scope, and let the GC collect the objects naturally. The .NET runtime is very efficient at managing memory as long as you don't try to do it's job.

EDIT

After reviewing the comments, I see you forgot to leave an important piece of information, in that you were binding the object in question to other objects methods. This means that the object that you are trying to finalize is not going to finalize until the method used to watch the event has finalized, thus keeping around a ton of extra objects in memory.

What you can do to break this strong reference is use an object called WeakReference. Or use lambdas to to break the strong references.

See this for an example of using a WeakReference http://msdn.microsoft.com/en-us/library/system.weakreference.aspx

Or you can do something like this:

dym.cas += (x, y, z) => gameTime.ElapsedGameTime(x,y,z);

instead of

dym.cas += gameTime.ElapsedGameTime;