Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
In .NET, are private methods and properties enforced by the runtime or just by the compiler?
If you try to call another object’s private methods, the compiler will throw an access exception. What if you manually manipulate the IL or try to call via reflection — will you be able to? Also, does it vary by runtime version (1.1 vs. 2.0 vs. 3.5 vs. 4.0)?
It is a compile time restriction. You can call private methods via Reflection in all versions of .NET. And starting in .NET 4.0, you can use
dynamicsto do it. In addition, using Reflection, you can see and use the methods behind automatic properties. It should go without saying that this isn’t recommended.