Is Reflection breaking the encapsulation principle?
c#, oop, reflection
Solution
Reflection breaks encapsulation principles by giving access to private fields and methods, but it's not the first or only way in which encapsulation can be circumvented; one could argue that serialization exposes all the internal data of a class, information which would normally be private.
It's important to understand that encapsulation is only a technique, one that makes designing behaviour easier, provided consumers agree use an API you have defined. If somebody chooses to circumvent your API using reflection or any other technique, they no longer have the assurance that your object will behave as you designed it. If somebody assigns a value of `null` to a private field, they'd better be ready to catch a `NullReferenceException` the next time they try to use your class!
In my experience, programming is all about assertions and assumptions. The language asserts constraints (classes, interfaces, enumerations) which make creating isolated behaviour much easier to produce, on the assumption that a consumer agrees to not violate those boundaries.
This is a fair assertion to make given it makes a divide-and-conquer approach to software development more easy than any technique before it.
Problem
Okay, let's say we have a class defined like ``` public class TestClass { private string MyPrivateProperty { get; set; } // This is for testing purposes public string GetMyProperty() { return MyPrivateProperty; } } ``` then we try: ``` TestClass t = new TestClass { MyPrivateProperty = "test" }; ``` Compilation fails with `TestClass.MyPrivateProperty is inaccessible due to its protection level`, as expected. Try ``` TestClass t = new TestClass(); t.MyPrivateProperty = "test"; ``` and compilation fails again, with the same message. All good until now, we were expecting this. But then one write: ``` PropertyInfo aProp = t.GetType().GetProperty( "MyPrivateProperty", BindingFlags.NonPublic | BindingFlags.Instance); // This works: aProp.SetValue(t, "test", null); // Check Console.WriteLine(t.GetMyProperty()); ``` and here we are, we managed to change a private field. Isn't it abnormal to be able to alter some object's internal state just by using reflection? Edit: Thanks for the replies so far. For those saying "you don't have to use it": what about a class designer, it looks like he can't assume internal state safety anymore?