Doubt about access specifiers in C#

Question

4.00/5 (1 vote)

See more:

C#

Why can't we use protected and protected internal specifiers prefixing class name

Posted 4-Jan-14 8:16am

Vinay Jade

Add a Solution

Comments

Karthik_Mahalingam 4-Jan-14 14:36pm

you can use it , that depends on the requirement....

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)

Ron Beyer · Accepted Answer · 2014-01-04T08:50:00

Root level classes, that is classes directly under a namespace, can either be internal or public. By default if you don't specify an access modifier, they are internal.

Classes defined inside other classes (nested classes) may be declared protected.

Why can't you use protected? Well protected means that the object is accessible to members of its declaring type, since root classes don't have a declaring type, they can't be protected from anything. "protected internal" doesn't make any sense after you get the concept I just described.