Why Interface methods are public by default ?

Question

0.00/5 (No votes)

See more:

C#

.NET

Why Interface methods are public by default ?
Why cant we have a protected method in interface ?

Posted 6-Jul-11 4:10am

adi007me

Add a Solution

Comments

Emrah Taylan 6-Jul-11 10:18am

If you want to take 'inherit' your interface and
if I want to override your methods you must declare 'protected' , protected couldn't use like public,

Do u understand? İf you want I can send you example code?

adi007me 6-Jul-11 10:19am

Little confusing ... Please send example code ...

1 solution

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)

fjdiewornncalwe · Accepted Answer · 2011-07-06T04:26:00

Solution 1

An interface is designed to provide a known and consistent "interface" to the outside world for classes that inherit it. There would be little point in having an interface with private methods defined.

Read up on the MSDN Documentation to understand better why this is the case.

Posted 6-Jul-11 4:26am

fjdiewornncalwe

Comments

Sergey Alexandrovich Kryukov 6-Jul-11 10:44am

Correct, my 5.
More exactly, private or protected methods won't be usable at all; and internal methods are not much needed as the whole interface can be declared internal with the same effect.

--SA

fjdiewornncalwe 6-Jul-11 12:26pm

Thanks SA

adi007me 6-Jul-11 13:55pm

Yes. It is not much useful, but is there any other design limitation in .net which doesn't allow this ?

Sergey Alexandrovich Kryukov 6-Jul-11 15:01pm

If you look at the answer and my comment properly, you will understand that this is not a limitation at all. If you add access modifiers to interface members, it won't be able to change interface usage at all.

When you're are asking about "other design limitations" what do you mean by "this". Listing ***all*** limitations would be like describing all language and CLS from scratch. :-)
--SA

adi007me 7-Jul-11 1:50am

Thanks SA.
I am also unsure about any design limitation, I was just confirming.

Sergey Alexandrovich Kryukov 8-Jul-11 1:18am

You post has a form of question; so my answer was that the lack of access specifiers in interfaces presents no limitations, due to the role of interfaces. Is there any doubt by now?
--SA