title: How do I test that all my expected web.config settings have been defined?
body: <p>I am using the built in test framework in VS2008 and I would like be able to write a test that makes sure all the expected web.config settings have been defined so that if by accident one is removed or changed my suite of tests will detect it and not have to be tested in a runtime scenario.  How would I set this up?</p>
  
  <p>I do not want to setup a mockup of my web.config since I don't want to maintain two versions and this would make my test invalid anyways since I am really trying to capture the fact that the project's web.config is correct.</p>
  
  <p>Any suggestions, alternatives, hints?</p>
  
  <p><strong>Solution:</strong> I ended up using the copy in the pre-build that was suggested with one change. On copy I rename the web.config to app.config so that the test project would automatically pick it up.</p>
  
  <p>I tried to split out the config files as suggested as well but the problem I ran into was when the test project ran, it actually didn't run out of the bin directory (which setting the config files to 'Content' type would copy to) but instead to a results directory that has been pre defined.  I could not figure out how to make it copy thos extra files to this results directory so the config files could never be found.</p>