Knowing the architecture and the generated code, layer by layer.

Introducing this topic, explanations and examples of codes generated and how they can be modified to meet the global and specific needs of each system.

To start, we present the .NET created solution. This is the structure generated for your project, dividing each schema into sub-folders, such as Contact and shop as shown below.

The layers are divided into:. Domain, Data.EntityFramework, Application, CrossCutting.IoC and Tests.


Structure in the layer Domain


 Note that artifacts are generated for sub-folders entities, enumerations, repository interfaces, service interfaces, unit of work interface resources of view and model of resources.

Here we show in detail codes generated for Entities


 Regarding the data access layer, we show below the structure created for Data.EntityFramework


Repositories classes are created for each found entity and the context classes and Unit of Work for using the entity framework.
We show below an example of implementations unit of work.


 Regarding the structure of the layer application are:


 An implementation class would be:


 In the layer of cross cutting, we have the following structure:


 And an example of implementation would be:


 On the web layer, we use the framework AngularJS with typescript and create the following breakdown:


 An implementation of a controller would be:


 In the service layer, the implementation of web api follow the following pattern: