I am building a Wpf MVVM Prism Unity application and want to make a property in the App class available to other modules through some sort of loose coupling methodology. As an example, let's say that there are database credential values in the application's
user settings (server, username, password, that sort of thing) that will need to be consumed by a module in a different assembly that will be responsible for actually implementing database operations. I was thinking that the App class could have a published
property that would read and write the property values from/to the application's user settings so that subscribers could utilize the information without being aware of the details of where that data actually resided. What is the appropriate way that such a
thing could be accomplished?
Richard Lewis Haggard