proteced vs internal vs protected internal

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:

image

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:

image

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

Liked this article? Support me on Patreon and get direct help from me via a private Slack channel or 1-2-1 mentoring.
Subscribe to my newsletter


Hi, I’m Yan. I’m an AWS Serverless Hero and the author of Production-Ready Serverless.

I specialise in rapidly transitioning teams to serverless and building production-ready services on AWS.

Are you struggling with serverless or need guidance on best practices? Do you want someone to review your architecture and help you avoid costly mistakes down the line? Whatever the case, I’m here to help.

Hire me.


Check out my new course, Complete Guide to AWS Step Functions. In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, callbacks, nested workflows, design patterns and best practices.

Get Your Copy