I'm not sure which would provide the best performance as well as an industry accepted solution. I have an application that is being used by a variety of customers now. Since we are now using a single code base I need to allow the customer(s) to configure options such as menu names, the mileage rate that they will pay for mileage as well as others. Is it accepted to utilize the web.config file to store the settings or should I go with a database solution? I've been reading a little on this subject and haven't really had my questions answered.
Which would provide the following:
* Easier to implement
* Provide performance increase (as far as setting/retrieving settings)
* Is one preferred over the other