You may have read on my recent posts about how the Visual Studio Configuration Manager again caused me problems for my BizTalk 2006 R2 project where the release/debug/deployment/development configuration settings seem to get out of sync and it ends up causing you various problems.
I got sick of this happening so I've created an MsBuild task which I can use in my build script to inspect the solution file and highlight any issues with the configuration. Basically the task will read through the file until it finds the settings section for this and when it compares the projects it will cause the build to fail if you get any projects set as Development & Release or Deployment & Debug.
Usually the configuration you want is Development & Debug or Deployment & Release.
It's a pretty straightforward task and the code is available on the below link so rather than walking through it, if it's of interest to anyone please just refer to the unit tests in the solution to see how it works.
If you build fails you will get a list of the line numbers which aren't right and you can correct them before you end up with weird errors later in your tests which take ages to troubleshoot like in one of my previous posts.
Hope this is useful to someone
http://www.box.net/shared/ben4vap98p