I've got a very large solution file, which currently has about 100 projects in it. It's not at all feasible to develop using the solution file as the build time for even the most trivial of changes is unreasonable. Now most of these projects are pretty stable, and rarely change, so I would like to create smaller solutions with the various dependency groups. I am, however, having a hard time doing this.
My problem is that if I make a "Dependencies" solution, which has say, 50 relatively stable projects in it, things at first seem to work well. I can have File references in my "main" solution referencing the 50 stable projects, and things all work... until I need to debug one of the 50 "stable" projects. As soon as I load one of my "stable" projects into my "main" solution, it has bad references. It's expecting a bunch of project references to the other 49 stable projects, but now it needs to use file references to them. Equally bad, none of the projects in my main solution detect that what was a DLL reference should now be a Project level reference. Even VB6 had this issue solved and working quite well. Has anyone come up with a solution to this issue using VS.NET ? -- Chris Mullins =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: NEW! Guerrilla ASP.NET, 17 May 2004, in Los Angeles http://www.develop.com/courses/gaspdotnetls View archives and manage your subscription(s) at http://discuss.develop.com
