title: .NET solution - many projects vs one project
body: <p>We currently have a rapidly growing C# codebase.  Currently we have about 10 projects, split up in the usual categories, common/util stuff, network layer, database, ui components/controls etc.</p>
  
  <p>We run into the occasional circular dependency where project x depends on something in y and vice-versa.  We are looking at maybe collapsing the projects down to one and just managing using structure folders/namespaces.  We have a Java project which of course organises just using folders/packages so we're not sure what, if any, benefit having multiple projects brings.  None of our projects require special project properties, except the main run project, which we may kept separate (and very thin).</p>
  
  <p>Does anyone have any prior experience in why one project is better/worse than multiple projects and could suggest the best approach?  And also any issues with circular dependencies would be useful in either approach would be useful.</p>
  
  <p>Any input appreciated.</p>