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.
Ideally I would like to place some properties in the App class for my WPF application to share between windows, dialogs, controls, etc. Is it trivial to reference those properties from other WPF components or should I just make them static for easier access?
In my opinion, the biggest issue in placing properties at the App class is that your code will be tightly coupled. Besides, the properties may be outside the scope of the App class.
If you don’t care about patterns, i.e., your application do not tend to grow in complexity, using properties in the App class may be a quick and easy solution. But if you do this in an already complex (or growing) code, it may lead you to a lot of headache.
If by making the properties static you mean put them in some class and reference it in another class, you get a less tightly coupled code, but not loosely enough.