With source control and a large development team, it seems much more
manageable to have one project per solution. Also, VS.NET performance
deteriorates as more and more projects are loaded into one solution. In
general, it tends to elminate all sorts of problems.
"Mike Moore" <Mi*******@discussions.microsoft.com> wrote in message
news:44**********************************@microsof t.com...
New to .Net! Should you create a class library in different solution than
the solution for your asp.net project is contained in? We are using the
isolated development mode and a single-solution approach for our web
projects.