Yan Cui
I help clients go faster for less using serverless technologies.
This article is brought to you by
The real-time data platform that empowers developers to build innovative products faster and more reliably than ever before.
Most C# developers will know what “public”, “private”, “protected” and “internal” access 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 4 ways I can help you:
- Production-Ready Serverless: Join 20+ AWS Heroes & Community Builders and 1000+ other students in levelling up your serverless game. This is your one-stop shop for quickly levelling up your serverless skills.
- Do you want to know how to test serverless architectures with a fast dev & test loop? Check out my latest course, Testing Serverless Architectures and learn the smart way to test serverless.
- I help clients launch product ideas, improve their development processes and upskill their teams. If you’d like to work together, then let’s get in touch.
- Join my community on Discord, ask questions, and join the discussion on all things AWS and Serverless.
http://www.samplecoder.com/2014/11/public-private-protected-internal-and.html[^]