Guidelines for solution source code organisation(OO/DDD)
        Posted  
        
            by fearofawhackplanet
        on Stack Overflow
        
        See other posts from Stack Overflow
        
            or by fearofawhackplanet
        
        
        
        Published on 2010-05-26T11:40:59Z
        Indexed on 
            2010/05/26
            13:21 UTC
        
        
        Read the original article
        Hit count: 216
        
.NET
|language-agnostic
|object-oriented-design
|domain-driven-design
|code-organization
I'm starting on my first business project (.NET) and am trying to follow DDD principles. Are there any guidelines or common patterns for orgaining source code and namespaces?
For example, do your domain objects go in a namespace MyProject.Domain or whatever? Would you separate the concrete implementations and the interfaces? In different namespaces? Different folders? Different solutions?
I know a lot of this is subjective and dependent on project size, but a few pointers or suggestions to get started on a relatively small but extensible n-tier project would be useful.
© Stack Overflow or respective owner