Hi,

Your question is very broad so it's difficult to give a specific answer. I think this can be a solid approach depending on the behavioral variation that you desire from your application.

Just to provide a very simple example, suppose that your application would connect to a particular resource (DB or web service for instance) depending on some characteristics of the user. You might provide those different resource strings (URLs or connection strings or whatever) though a config file.

I submit that many folks use config to vary thier app's behavior to avoid recompiliation. Of course WCF makes extensive use of config files. As do ASP.NET web sites.

There are some limitations to config files. If you want to vary the behavior that's provided through a DLL, the config has to go parent exe's file.

Does this help? Again, without knowing the specifics,