I'd like to add to this post by asking a further question...

We have a very large solution (over 170 projects) which is just too big to
manage properly. Therefore my team has created a smaller solution that
contains only the subset of the projects that are relevant to our day to day
work - including unit testing.

However, even the smaller solution has plenty of projects in it (40 - C++
mostly). 5 of these are unit test projects which now contain in excess of 200
unit tests. The problem we're having now is that it takes an age for the Test
View to refresh. It seems that when you refresh (or load the view for the
first time) the IDE (Intellisense I think) scans the entire solution for unit
test code. Is there any way to optimise this so that it doesn't have to
rescan the entire solution when we need to refresh the Test View?

I really need a solution to this as my team is piloting Unit Testing before
rolling it out to the rest of the development group as a whole. If we can't
find a way to make the Unit Testing scale better then I can only see that
we're going to have to find an alternative. We're using VS2005 by the way -
does anyone know if the situation is any better in VS2008?

Possible solutions we're considering:
1) Removing even more projects so that we have a "test" solution that only
contains the projects under test and their associate test projets. (But even
that will eventually get big again).
2) Moving to NUnit - or perhaps TestDriven.Net?

Thanks.