Introduction to the chesframe framework

I have always wanted to write a framework for the following purposes:

1. Summarize previous projects

2. It saves the cost of building the system and does not need to start from scratch every time.

3. Writing and using the framework is constantly improving. This is also a collection process.

After more than a month, a basic prototype is built. The following figure shows the structure:

The structure is mainly divided into two parts: the portal end and the service end, the call relationship from top to bottom.

Below is a brief introduction of each layer:

1.asp.net MVC front-end site. The MVC mode is used to appreciate the processing logic of MVC. The powerful AOP features and scalability make it much cleaner without webcontrol.

2. facade layer, mainly used to call services and convert between model and Entity

3. the WCF Service layer includes two layers, the interface layer and the implementation layer, and the WCF Service structure at night

4. bizprocessor business logic processing layer to process all business logic

5. dataaccesslayer: use interfaces to facilitate underlying replacement

6. Database Layer

7. The entity layer runs through the facade to the data access layer. There is no strict difference between DTO and entity, which is unified as entity.

8. The utility layer runs through the entire application.

 

Next, we will introduce the specific implementation and encapsulation of one layer and one layer.

There are four main parts:

1. Data Access

2. WCF

3.asp.net MVC

4. Other Utility

Each part will introduce each part of the content, which will be described in a separate chapter: encapsulation of the data access layer, and the combination of configuration-free running and configuration-based running of WCF, there may be some interesting ideas about Exception Handling in WCF, extension of Asp.net MVC, and exception handling.