title: Managing web.config for teams in VS2010 & TFS
body: <p>With VS2010's mandate that web.config be included in the project, how do we allow everyone to keep their own custom config file without getting into source control problems?</p>
  
  <p>Previously, we would simply leave web.config out of our project, allowing everyone to keep their own local version of web.config on their machine. We moved to VS2010, and it is now forcing me to add web.config to my project in order to run debug mode. Because our project is linked to TFS, it automatically adds web.config to source control and tries to maintain it that way.</p>
  
  <p>Is there a way to run in debug mode without including web.config in your project? Or is there a better way to manage config files?</p>