Do we call Dispose for disposing managed objects even?

Question

0.00/5 (No votes)

See more:

Hi,

Do we call Dispose method even for managed objects? If it is for only for Unmanaged objects, why do we call GC.SupressFinalize() method at the end of Dispose?

Thanks,
D Apparao

Posted 24-Apr-13 21:17pm

Mr Apps

Add a Solution

2 solutions

Solution 1

You need to dispose all objects that implements IDisposable. That's why they implement IDisposable interface.

GC.SupressFinalize requests that the system not call the finalizer for the specified object. (GC=Garbage collection) SuppresFinalize should only be called by a class that has a finalizer. It's informing the GC that this object was cleaned up fully.

Posted 24-Apr-13 21:44pm

StianSandberg

Comments

Mr Apps 25-Apr-13 4:07am

When do I need to implement IDisposagle interface? I did not get your point "SuppresFinalize should only be called by a class that has a finalizer". Can you please make this more clear?

StianSandberg 25-Apr-13 4:47am

You need to implement IDisposable in your classes if you have to clean up anything after it has done it's job. Then you can run som code after object is used.
A class can also have a "destructor" (MSDN Destructors (C# Programming Guide)). Using GC.SupressFinalize you tell the object not to "execute" this destructor.

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

radioman.lt · Accepted Answer · 2013-04-24T21:46:00

Solution 2

it's not for only unmanaged object, it's for both

SupressFinalize just disabled so called 'destructor' because we already manualy destroyed the object

Posted 24-Apr-13 21:46pm

radioman.lt