what's real advantage of using Interface

Question

4.00/5 (2 votes)

See more:

C#

public interface IDisposable
{
   void Dispose();
}

------------------------------------------

C#

public class MyClass : IDisposable
{
    public void Dispose()
    {
        // Perform any object clean up here.

        // If you are inheriting from another class that
        // also implements IDisposable, don't forget to
        // call base.Dispose() as well.
    }
}

----------------------------------------

here in above what's real use of Interface Disposable. why can't the Dispose menmber directly implemented instead
we have to implemenmt Idisposable & then write functionality inside in dispose method.This looks like a long way.

First we have to create class then we have to define method name alone & then the class is finally implemneted
& then the fuctionality is to be written in Dispose method. so what's advantage here.

Posted 28-Jan-13 0:28am

anbujeremiah

Updated 28-Jan-13 0:58am

Richard MacCutchan

v2

Add a Solution

4 solutions

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)

Richard MacCutchan · Answer 1 · 2013-01-28T00:55:00

Solution 1

If your class implements the IDisposable interface, then it must provide its own implementation of the Dispose method. See Implementing IDisposable and the Dispose Pattern Properly[^].

Posted 28-Jan-13 0:55am

Richard MacCutchan

Updated 28-Jan-13 0:57am

v2

OriginalGriff · Answer 2 · 2013-01-28T00:59:00

Not everything is Disposeable - or needs to be. It's only when it contains resources which need to be returned to the system that you need to implement Dispose, so when it it implemented, that is a good sign that you should either be calling Dispose on it when you are finished with it, or you should be creating it within a using block.

If it was always available, it would just make it harder to know if the class instances should be disposed - and most don't so they don't have a Dispose method to call.

Jameel VM · Answer 3 · 2013-01-28T01:08:00

Solution 3

Please go through this link.
http://stackoverflow.com/questions/538060/proper-use-of-the-idisposable-interface[^]

Hope this helps

Posted 28-Jan-13 1:08am

Jameel VM

**Joezer BH** · Answer 4 · 2013-01-28T04:47:00

I'd say you'll do good to read about Interfaces in general, and the uses they have.

Though it's true for the specific IDisposable Interface,
Basically: Interfaces expose and impose functionality on classes that implement them so that the class follows the Interface guidelines and then it is sure to provide. On the other hand the class using another class can rely on the fact that it knows the functionality is has to implement.

Implementing IDisposable is signaling that this class is implementing the Dispose function and is doing "what is needed" to be done inside to dispose of the objects and data and so forth that is has under it's management.

Cheers,
Edo

what's real advantage of using Interface

4 solutions

Solution 1

Solution 2

Solution 3

Solution 4

Add your solution here

Preview 0