ASP.NET 2.0 Web Sites and Project Dependencies
I have had the occasional report that TestDriven.Net doesn't always build project dependencies. Until recently I hadn't been about to consistently repro this. It now seems the issue is related to having an ASP.NET 2.0 Web Site as part of a solution. For some reason as soon as a web site is added to a solution the dependency checking breaks down. This even happens even with unrelated projects that were working fine before.
I now have what seems to be an effective workaround. Instead of using the 'SolutionBuild' Visual Studio automation object, I'm now directly invoking the build command. If you would like to help test the workaround, please drop me an email.