Came across an odd situation while setting up Continuous Integration for a solution in TFS today.  Each build would pass, but none of the unit tests were being run.  On inspection of the log it turns out a warning was being generated…

If you change the default application name on the web tab of the project properties in your asp.net project, and you have previously compiled your project, you may find some strange errors stand in your path when you go to run your project.  This is because the dll names that the build outputs in your bin directory have changed, and when you go to run your application, asp.net sees both sets – the old and the new, and loads them both.  Cleaning your solution will not rectify the issue because as far as asp.net is concerned, they are not an output of the build, so it respects the fact that you may have put them there manually (but you wouldn't do that in a web application project anyway, right?).  Just delete the old dlls (and pdb if its there) and you are good to go.  This happened to me in an asp.net mvc project and it complained that my routes already existed.

This usually means that a provider specified in one of your web.config connection strings is not installed on your machine.