Wednesday, July 30, 2008 10:16 AM
I recently just upgraded a branch of our solution from VS2005 to VS2008 using the upgrade wizard. All projects upgraded easily except for a few. After a second look, I noticed all of those projects were unit test projects. In fact, they were all MSTest unit test projects.
We use MbUnit and NUnit for our unit tests so we had abandoned the MSTest projects some time ago. This was mainly because I got tired of watching Visual Studio hang for 2 – 3 seconds to load that stupid Testing Toolbar just because I accidentally clicked on one of the MSTest projects in the solution explorer. However, there were a few remnants still hanging around that we just hadn’t gotten to. If you have a similar situation, here’s how to fix the problem…
1) Click on the “unavailable” project in the Solution Explorer and choose “Edit MyProject.csproj”
2) The project file will open in the Visual Studio editor. Locate the <ProjectTypeGuid> element and remove the value {3AC096D0-A1C2-E12C-1390-A8335801FDAB}. This it the value that identifies the project as an MSTest project. You can find a list of more project type guids here.
3) Click the “unavailable” project in the Solution Explorer and choose “Reload”
4) Voila.