-
Book Overview & Buying
-
Table Of Contents
Clean Architecture with .NET
By :
A natural response to the growing density of Program.cs is to introduce clearer structural boundaries. Rather than allowing service registrations and implementation details to accumulate in a single project, we separate responsibilities into distinct projects—typically Presentation, Application, and Infrastructure. This structural separation is a meaningful step forward because it reflects the architectural intent of the system more clearly.
This is the direction we took earlier in the book. Infrastructure concerns were moved into their own project. Application logic was isolated from frameworks and external dependencies. The Presentation layer was given a single integration point for infrastructure through a method such as services.AddCoreLayerServices(configuration). Instead of wiring up database connections, repositories, and other external concerns directly in Program.cs, that responsibility was centralized within Infrastructure. The Presentation...