Visual Studio performance for solutions with a large number of projects truly, truly sucks… I am working on a project right now which has 78 projects in a solution, including installer projects, unit tests, UI stuff, etc.
I know what you are thinking: “The problem isn’t VStudio, the problem is the idiot who built a solution with 78 projects”. If you were thinking that, you are right. The problem here isn’t the scalability of VStudio, but “project sprawl” but here is the lesson I am trying to burn into my brain… Every time you create a new project, class library, unit test project, etc, ask yourself: “Do I really need this?” Chances are, you could just add a new folder to an existing project. It would save hours and hours of refactoring piles of projects and project references, dependencies, etc into a smaller number of workable projects.
Lesson duly learned…
Posted by Brandon P Miller 