asp.net - Synchronizing External Configuration Between IIS Servers in a Web Farm -

. I do not necessarily need the web. Concerned about config, as I am concerned about other configuration files which are present in the application.

For example, we store the caching policies in the external XML file, where it has its own schema, and it will soon have its own tool to maintain values, after implementing the changes, Must be rushed to the farm.

Some scenarios on which I have considered so far:

• Robocopy, replication, or even equivalent, it is necessary to work only on a specific node of the field. (Push to the app.)
• The configuration server is stored on all external configurations and their device is a physical example of IIS. The application will retrieve these configuration files for the application and for voting for changes from time to time. (App selection.)
• Team Build We can host the device in-house and set up a post-build process to deploy files. (App selection.)
• Database storage applications can read and select the database for configuration (app choice.)

In all these scenarios, Professionals and Oppositions I'm not sure what the best solution is, even though I think that there can be a clear view of policing applications for changes, the question is whether you want to fulfill it Will good idea?