501

What is the difference between the internal and private access modifiers in C#?

1

7 Answers 7

621

internal is for assembly scope (i.e. only accessible from code in the same .exe or .dll)

private is for class scope (i.e. accessible only from code in the same class).

Sign up to request clarification or add additional context in comments.

6 Comments

i have a quick question; if i declare a class as private in a namespace within an assembly versus the class being internal, i can access that class within the assembly in both cases, then what is the difference between a private class and an internal class? or is private and internal modifiers in terms of classes used when nesting class within class?
i added the specific project/assembly as a reference of another project and both private as well as internal prevent me from accessing this particular class within the namespace, so then again... difference between private and internal classes is? thanks
You cannot declare a top level class as private. The compiler will stop you.
@NetSkay: If you declare a private class inside a public class then this class is not accessible by other classes in your assembly but if you declare this class as internal then it would be accessible in the assembly. Although, they both will not be accessible outside the assembly.
If you are coming from a VB.NET background, C#'s "internal" keyword is equivalent to VB.NET's "Friend" keyword.
|
258

Private: Private members are only accessible within the own type (Own class).

Internal: Internal member are accessible only within the assembly by inheritance (its derived type) or by instance of class.

enter image description here

Source: dotnetbull - what is access modifier in c#

6 Comments

Interesting that Protected Internal provides wider access than Protected.
@Dan, thoroughly agree. It might be helpful to read and think of protected internal asprotected OR internal.
What does With Type mean?
@Dan yeah, i assumed it would just act as a truth table and AND that matrix to true|false|false|false for protected internal. not intuitive. instead it's true|true|true|false as if OR'd.
Incidentally, C# 7.2 just added a "protected AND internal" modifier, though the actual keywords chosen, private protected, aren't very intuitive. For details: learn.microsoft.com/en-us/dotnet/csharp/language-reference/…
|
80

internal members are visible to all code in the assembly they are declared in.
(And to other assemblies referenced using the [InternalsVisibleTo] attribute)

private members are visible only to the declaring class. (including nested classes)

An outer (non-nested) class cannot be declared private, as there is no containing scope to make it private to.

To answer the question you forgot to ask, protected members are like private members, but are also visible in all classes that inherit the declaring type. (But only on an expression of at least the type of the current class)

Comments

11

internal members are accessible within the assembly (only accessible in the same project)

private members are accessible within the same class

Example for Beginners

There are 2 projects in a solution (Project1, Project2) and Project1 has a reference to Project2.

  • Public method written in Project2 will be accessible in Project2 and the Project1
  • Internal method written in Project2 will be accessible in Project2 only but not in Project1
  • private method written in class1 of Project2 will only be accessible to the same class. It will neither be accessible in other classes of Project 2 not in Project 1.

Comments

9

Private members are accessible only within the body of the class or the struct in which they are declared.

Internal types or members are accessible only within files in the same assembly

2 Comments

so whats the difference in using this? i still dont get it :X
Private are accessible from within the Class only, Internal is accessible from within the Assembly (project in VS i.e. dll / exe file).
9

private - encapsulations in class/scope/struct ect'.

internal - encapsulation in assemblies.

Comments

4

Internal will allow you to reference, say, a Data Access static class (for thread safety) between multiple business logic classes, while not subscribing them to inherit that class/trip over each other in connection pools, and to ultimately avoid allowing a DAL class to promote access at the public level. This has countless backings in design and best practices.

Entity Framework makes good use of this type of access

Comments

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.