Projects and dependencies in ABP learning solutions

.Domain.Share project

The project contains constants 、 Enumerations and other objects , These objects are actually part of the domain layer , But all the layers in the solution / Projects will use . For example, entity class Book Enumeration used in BookType、 Constant BookConsts  Are suitable for this project .

This project does not depend on other projects in the solution , Introduction to other projects or directly rely on this project

.Domain  project

The domain layer in the solution , contain Entity , Set root , Field service , Value type , Warehousing interfaces and other domain objects of the solution . For example, entities and IBookRepository Classes are suitable for this project

It relies on .Domain.Share Because it may be in the application interface and DTO Use constants in 、 Enumeration or other shared objects .

.Application.Contracts project

  The project mainly includes application services interfaces And application layer data transmission objects DTO, It is used to separate the interface and implementation of the application layer , In this way, the interface project can be shared to the client as a contract package .

for example IBookAppService Interface and BookCreationDto Classes are suitable for this project

It depends on .Domain.Share because   He may be in the application interface and DTO Use constants in 、 Enumeration or other shared objects .

.Application project

Project contains .Application.COntracts Implementation of the application service interface of the project .

for example BookAppService Class is suitable for this project

It relies on .Application.Cantracts project , Because it needs to implement interfaces and use DTO                                    It depends on .Domain.Share because   He may be in the application interface and DTO Use constants in 、 Enumeration or other shared objects .

.EntityFrameworkCore project

Integrate EF Core project , Defined DbContext And implement .Domain Warehouse interface defined in the project  

It relies on .Domain project . Because it needs to reference entities and warehousing interfaces  

.EntityFrameworkCore.DbMigrations project

Included in the solution EF Core Database migration for , It has independent DbContext To specifically manage migration

ABP It's a modular framework , The ideal design is to let each module have its own DbContext class , This is for migration DbContext It will work , He will all DbContext The configuration is unified into a single model to maintain the schema of a single database , For more advanced scenarios , Programs can have multiple databases ( Each database has one or more module tables ) And multiple migrations DbContext( Each maintains a different database schema )

We need to pay attention to , transfer  DbContext  For database migration only , Instead of Runtime Use .

• It relies on  .EntityFrameworkCore  project , Because it reuses the  DbContext  To configure  

.DbMigrator project

This is a console application , It simplifies database migration in development and production environments , When you use it ：

Create a database when necessary （ Without a database ）

Apply data migration without migration

Initialize seed data （ When you need it ） 

Although creating databases and applying migrations seems only useful for relational databases , But even if you choose NoSQL Database provider ( Such as MongoDB), This project will also be generated . At this time , It will provide the necessary initial data for the application .

• It relies on  .EntityFrameworkCore.DbMigrations  project ( in the light of EF Core), Because it needs to access the migration file .
• It relies on  .Application.Contracts  project , Because it requires access permission definitions to give all permissions to the administrator user when initializing seed data .

 

 .HttpApi project

Used for definition API controller

Most of the time , You don't need to define it manually API controller , because ABP The dynamics of the API The function will be automatically created according to the application layer API controller , But if you need to write API controller , Then it is the most suitable place

It relies on .Application.Contracts project , Because it needs to inject the application service interface

 .HttpApi.Client project

Definition C# The client agent uses... In the solution Http API project , You can share your edits to third-party clients , Make it easy in DotNet Use your http API

ABP Yes dynamic C# API client function , So in most cases, you don't need to create it manually C# Client agent .

.HttpApi.Client.ConsoleTestApp  The project is a console application that demonstrates the use of client agents .

• It relies on  .Application.Contracts  project , Because it needs to use application service interface and DTO.

If you don't need to be API Create dynamic C# Client agent , You can delete this project and dependencies

.Web project

  Contains the user interface of the application (UI). If you use ASP.NET Core MVC UI, Contains the main of the application  appsettings.json  The configuration file , Used to configure the database connection string and other configurations of the application

rely on  .HttpApi  project , because UI The layer needs to use the... Of the solution API And application service interface . 

. Hierarchical structure

If you choose ASP.NET core UI And designated --tiered Options ,CLI Will create tiered solutions , The purpose of the hierarchical structure is to Web Applications and Http Api Deploy to different servers

References ：Startup Templates/Application | Documentation Center | ABP.IO 

The purpose of writing this article is to facilitate my study ABP