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.
Seems like every C# static analyzer wants to complain when it sees a public field. But why? Surely there are cases where a public (or internal) field is enough, and there is no point in having a property with its get_ and set_ methods? What if I know for sure that I won’t be redefining the field or adding to it (side effects are bad, right?) – shouldn’t a simple field suffice?
Because it breaks encapsulation — this is why most people use accessors heavily. However, if you think it’s the right solution for your task, ignore it (meaning the strict encapsulation complaints) and do what’s right for your project. Don’t let the OO nazis tell you otherwise.