This sample application aims at dealing with the creation, edition and persistence of some TODO items and lists.

This way efforts can be put into the Domain modelisation within being cluttered by those aspects. Application’s aspects like persistence, business rule, network access… are totally absent from the Domain. NET CLR primitive types ( int, string, Exception…). Clean Architecture is inspired from Domain Driven Design (DDD).

Dependencies flow toward the innermost circle which is the Domain.

We refined this diagram with the responsibilities and roles of each project:

This Clean Architecture can be explained through an onion-architecture diagram: one concentric circle for each project in src. Application code and test code are explicitly separated through a src and tests solution folders. Here is the Visual Studio Solution Explorer view of this Clean Architecture solution. It illustrates well how an ASP.NET Core application can benefit from Clean Architecture principles. NET solution template available here on github recently updated to support. In this post we’ll explore the Jason Taylor’s CleanArchitecture.

Arch visual studio code