proteced vs internal vs protected internal

Yan Cui

I help clients go faster for less using serverless technologies.

Most C# developers will know what “public”, “private”, “protected” and “internalaccess modifiers mean and would have had to use them in their code, but rarely do we come across the “protected internal” access modifier.

Now, protected means the type or member can be accessed by derived classes, NOT restricted to the same assembly, whereas internal means the type or member can be accessed by code ONLY in the same assembly. It’s easy (and common) to think of the access modifiers in a linear sense where private is the most restrictive, and protected, internal and ultimately public becomes less and less restrictive:


This is certainly the case within the SAME assembly, but when you have multiple assemblies this no longer holds true as types might be derived outside of the assembly it’s declared in:


And that is what protected internal gives you – accessibility from any derived classes anywhere, as well as any class from within the same assembly.

Whenever you’re ready, here are 3 ways I can help you:

  1. Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game.
  2. Consulting: If you want to improve feature velocity, reduce costs, and make your systems more scalable, secure, and resilient, then let’s work together and make it happen.
  3. Join my FREE Community on Skool, where you can ask for help, share your success stories and hang out with me and other like-minded people without all the negativity from social media.


1 thought on “proteced vs internal vs protected internal”

Leave a Comment

Your email address will not be published. Required fields are marked *