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.
Note: application, as opposed to libraries.
I’ve got a WPF application. It’s broken down into a main application project and associated class libraries.
Are there any circumstances where any of the classes in the main application need to be public, as opposed to internal? For example, do data bindings or WPF value converters need to be public, if the XAML is in the same assembly?
Unless you are planning on referencing your EXE from another application, there is no reason your classes can not exclusively be
internal.