Remote client configuration

I'm looking for an approach: We have several applications that work with third-party applications. The settings of our applications have开发者_JAVA百科 to be changed regularly (e.g. with every event, the third party tools require changed config items). The mentioned settings reside in the config-Files of our applications. Those applications are mostly operated in a LAN.

How can those changing (and required) settings be distributed in a elegant way so we change the settings once and the other applications pull those settings? Are there existing components in .net? How would you approach this problem? Maybe create a service and make all the applications act as config clients? Hope for some ideas!

---

Create an updater for all distributed application (this will be one time update) and distribute one more time. That updater will read the updates from server and update the application config, and restart itself. You should have versions or date time stamp so that your updater will update only when there is change in your DB. BigL approach wont work if application is not online, but this will. You can skip the update if service is not available.

---

That's an interesting question maybe you could try to store the settings in a central database and your applications would load the settings from there directly or through a service. I think i would choose a compact sql database.

And you need to store the settings in app.config too and if you start your app then look for the service and if available then update the settings in the local config if needed.