title: How to Organise a Domain Driven Design Project?
body: <p>I've started learning about DDD and wanted to know how others have organised their projects.</p>
  
  <p>I've started off by organising around my AggregateRoots:</p>
  
  <p>MyApp.Domain (namespace for domain model)<br><br></p>
  
  <p>MyApp.Domain.Product <br>
  - Product<br>
  - IProductService<br>
  - IProductRepository<br>
  - etc<br><br></p>
  
  <p>MyApp.Domain.Comment<br>
  - Comment<br>
  - ICommentService<br>
  - ICommentRepository<br>
  - etc<br></p>
  
  <p>MyApp.Infrastructure<br>
  - ...<br></p>
  
  <p>MyApp.Repositories<br>
  - ProductRepository : IProductRepository<br>
  - etc<br></p>
  
  <p>The problem i've bumped into with this is that i have to reference my domain product as MyApp.Domain.Product.Product or Product.Product.  I also get a conflict with my linq data model for product....I have to use ugly lines of code to distiguish between the two such as MyApp.Domain.Product.Product and MyApp.Respoitories.Product.</p>
  
  <p>I am really interested to see how others have organised their solutions for DDD...</p>
  
  <p>I am using Visual Studio as my IDE.</p>
  
  <p>Thanks alot.</p>