title: Naming: solution, projects, namespaces and assemblies
body: <p>I'm working on naming guidelines for solutions, projects, their default namespaces and assemblies (Visual Studio).
  Now it looks like that:
  For example, we have a company named "Company" and a project named "Project". The project has business logic in separate dll, UI (WPF/WinForms) and a web part. There are names of things listed in the question title:</p>
  
  <p>Solution name: "Project".</p>
  
  <p>Business logic dll project name: "Project", default namespace: "Company.Project", assembly name: "Project".</p>
  
  <p>UI project name: "ProjectUI", default namesapce: "Company.Project.UI" (it can be extended in case of multiple versions of UI, like "Company.Project.UI.WPF"), assembly name "Project" (working because it's not a dll).</p>
  
  <p>Web project name: "ProjectWeb", default namespace: "Company.Project.Web", assembly name: "ProjectWeb" (for web applications).</p>
  
  <p>My questions are: do you have guidelines like that? Is it a good idea to describe thoose things? What you think about my approach?</p>
  
  <p>I'll be glad if you share ways that you use in your work.</p>