asp.net big applications, several developers and manage changes of web.config file

Question

Hi Guys,

The problem - a big asp.net applications (libs, frameworks, models, everything inside) having web.config file and several developers work on this project. How to make the same "core" shared between all of them, so they don't change the core, but only change the user-specific values that never comes back into code (mercurial) repository, so it doesn't affect other developers.

Like error reporting, tracing or connectionStrings?

any ideas? user.config is not a full solution, since it only allows only app.settings rewriting and not the connectionStrings section. Any ideas, solution? SO I'd like the option when lead developer push core changes to web.config that everybody gets, but they never do it manually, plus their local changes never committed back to repository so others are affected.

Thanks, Dmitry

Answer 1

Hi Dmitry, Take a look at configsource. You could put your "core" settings in a seperate config file and exclude from your source control. Then each of your developers could have their own connection strings etc.

http://weblogs.asp.net/fmarguerie/archive/2007/04/26/using-configsource-to-split-configuration-files.aspx

Cheers Tigger