Should I use separate projects for limited context in DDD.NET?

Question

We discuss how to implement Domain Driven Design.

Are there any immediate flaws in using a separate project for each limited context?

All thoughts and suggestions on our approach are welcome.

So it will look like this:

- ProjectA.dll (User Context Web Service)
    - References 
        - ProjectB.dll

- ProjectB.dll (User Context Domain)

- ProjectC (Web App)
    - References
        - ProjectD.dll
        - REST calls to ProjectA for User stuff

- ProjectD.dll (Product Context Domain)

- ProjectE.dll (Some Other Context)
    - Domain
        - Service
            - IService.cs
        - DTO
            - DTO A.cs
        - Entity
            - Entity A.cs
            - Entity B.cs
    - Repository
        - Repo.edmx

We are considering creating a limited context only through web services to provide scalability to areas that can receive heavy traffic.

Answer 1

, . , BC.

( ) :

, BC, - a BC.

, .

1: BC

, ( BC ). , VS .

2: BC

, . BCs . .

---

, , . , . BC. .

Answer 2

, , , , , . ( #, Visual Studio).

, . , . , .

, ...