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.
I have an application.
I login.
I make a web call and get a bunch of settings.
I publish an eventaggregator event that sends these settings to any other class that wants to listen and grab them.
To me this just seems like the wrong design. For a loosely coupled project what is the best way to share a bunch of settings in a class? I know I could make a static global, but that does not sound loosely coupled either!
You may define
ISettingsProviderinterface and use dependency injection and IoC containers like Unity or Autofac to inject this interface implementation to any class you would like to and use it there.It will be loosely coupled because you will not have dependency to real setting provider implementation and it will be possible change implementation easily (e.g for unit testing).