Solved

Clarification on 'Internal' access modifier in c#

Posted on 2010-09-23
7
361 Views
Last Modified: 2012-06-27
I have been revising for an upcoming test on .net/c# and would like to clarify something. I like to fully understand things before I 'tick' them off in my head.

So, within .net, we have the following access modifiers;

Public (no problem here)
Private (no problem here)
Protected (no problem)

However, I am a little confused with the 'internal' and then subsequent 'protected internal'

The MSDN explanation of 'internal' is "Access is limited to the current assembly."

Now,my understanding of an assembly is a collection of modules and resources compiled into an 'assembly' be that .exe or .dll

So based on this assumption, how can an internal modifier be limited to an assembly, based on this;

I have an 'assembly' in which i have various files, which contain my custom classes. If I declared an 'internal' value (int) in one of these classes, it will compile. If I then instantiated this class from another assembly (my ui), I can access it.

Now I do see that when you create an 'internal' class, then it is inaccessible from another assembly. So, what about the internal value (int). Am I basically breaking an unwritten rule by declaring my value (int) as internal or am I missing something completely.

Although not tested, I would assume the same is going to come up with protected internal to some degree.

Can anyone clarify this for me.



0
Comment
Question by:officedog
7 Comments
 
LVL 29

Expert Comment

by:anarki_jimbel
Comment Utility
OK, from my experience.
I use internal modifier mainly for some methods is classes. This means I can access these methods only in the current project (which will be compiled into an assembly). The main reasoning to have these methods only inside the project E.g., I have a project for all my user controls. And, e.g., I have some specific MyTextBox that is used by some other controls, e.g. by MyComboBox. Outside the project I want to use both MyTextBox and MyComboBox. But some methods of the MyTextBox should be used by MyCombo, therefore I mark them as "internal. So, they look like "public" inside the project but not visible outside.
0
 
LVL 29

Expert Comment

by:anarki_jimbel
Comment Utility
Protected internal is used to deny access to parts of a class' functionality to any descendant classes found in other applications. In other words, if I inherit a class with a protected internal method in another project - I should not see it.

0
 
LVL 9

Expert Comment

by:shadow77
Comment Utility
Private is restrictive; it only allows access by members of the class in which the variable or method is declared.

Public is non-restrictive; it allows access from anywhere.

Internal and Protected fall in between.  Internal is like "public, but only withing this assembly", while protected is like "public but only for the declaring class and its sub-classes"

Protected Internal means Protected or Internal, that is "public within this assembly or within this class and its sub-classes".
0
Maximize Your Threat Intelligence Reporting

Reporting is one of the most important and least talked about aspects of a world-class threat intelligence program. Here’s how to do it right.

 
LVL 26

Accepted Solution

by:
Anurag Thakur earned 125 total points
Comment Utility
0
 
LVL 29

Assisted Solution

by:anarki_jimbel
anarki_jimbel earned 125 total points
Comment Utility
The first link from ragi0017 is a good one. I'll try to explain it in my interpretation. I just did some testing and found thew following.

1. If a method is marked as "protected internal" - this means that for the current project (assembly) it's both internal, i.e. can be visible anyway in the current project. And it can be inherited as any protected method. In other words, does not make big difference in the same project: it could be marked as public or just internal.

2. For another project we haver some difference. If we create a class MyTestClass2  inheriting from the first project's class MyTestClass, protected method will be inherited and will be visible inside the new class. I.e., "internal" does not work for inheritance.
However, if we try to create an instance of the MyTestClass  in the second project:

TestProj1.MyTestClass c = new TestProj1.MyTestClass();

the method won't be visible for the "c" object, because the method is "internal" for the first project.

Hope it's not too confusing.
0
 

Author Comment

by:officedog
Comment Utility
Great got it all now thanks. I think the biggest help was this statement from the page that ragi0017 linked.

'protected internal' does not mean protected *and* internal - it means protected *or* internal.  

Thanks all :)

0
 

Author Closing Comment

by:officedog
Comment Utility
Closed. Points awarded to ragi0017 and anarki_jimbel.
0

Featured Post

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

Suggested Solutions

Extention Methods in C# 3.0 by Ivo Stoykov C# 3.0 offers extension methods. They allow extending existing classes without changing the class's source code or relying on inheritance. These are static methods invoked as instance method. This…
Entity Framework is a powerful tool to help you interact with the DataBase but still doesn't help much when we have a Stored Procedure that returns more than one resultset. The solution takes some of out-of-the-box thinking; read on!
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
You have products, that come in variants and want to set different prices for them? Watch this micro tutorial that describes how to configure prices for Magento super attributes. Assigning simple products to configurable: We assigned simple products…

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now