title: Project structure recommendation for an opensource asp.net mvc project
body: <p>What do you think of the project structure for an opensource CMS application built on asp.net mvc application?  The project nickname is "Gol".</p>
  
  <p>The basic requirements are outlined in the following posts.</p>
  
  <p><a href="https://stackoverflow.com/questions/325182/ideas-for-opensource-cms-in-asp-net-mvc">Ideas for OpenSource CMS in ASP.NET MVC</a></p>
  
  <p>Currently I am thinking of laying it down like this...</p>
  
  <ul>
  <li>Gol.Core.Session  (contains session manager both real and fake)</li>
  <li>Gol.Core.Caching (contains caching including velocity, enterprise lib. provider)</li>
  <li>Gol.Core.Logging (contains logging components and providers)</li>
  <li>Gol.Core.Instrumentation (contains instrumentation related items)</li>
  <li>Gol.Core.UI  (UI helpers, and other things related to UI)</li>
  <li>Gol.Core.Security (security,authentication related things)</li>
  <li>Gol.Core.Utilities (common utility functions like encryption, helper methods, etc).</li>
  <li>Gol.Core.Metadata (metadata manager).</li>
  <li><p>Gol.Web.Controllers (all controllers goes here).</p></li>
  <li><p>Gol.Cms.Contracts  (contains the service contracts)</p></li>
  <li>Gol.Cms.Model (contains the service model)</li>
  <li><p>Gol.Cms.Services (contains the service implementation).</p></li>
  <li><p>Gol.Web (the web project that contains the views)</p></li>
  <li>Gol.Test (or Gol.Specification)</li>
  </ul>
  
  <p>What do you think?  Is the structure overloaded/bloated? </p>
  
  <p>Your thoughts/suggestions welcome based on your experience (nothing specifically do with asp.net mvc).</p>
  
  <p>This may help others as well who may be interested in designing the initial project structure.</p>