Build a backend management system for ASP. Mvc5+ef6+easyui 1.4.3+unity4.x Injection (60)-System Summary

Objective:

When I first wrote this frame, I could say that it was not a very popular design pattern at the time, it was in the 2012, object-oriented programming was familiar to everyone, but "injection, control inversion (DI,IOC, Dependency Injection), AOP programming" emerging nouns

Many people do not know especially to engage. NET developers, at least at the time, but today they are very popular technical indicators, many Daniel also admitted that this is the mainstream development model, you can see from the recruitment network of technical posts.

Hey...

I have been involved in MVC2.0 to 5.0 development work, witnessed the maturation of MVC evolution process, like this framework, the design pattern has not changed, but the code has been refactoring. I also believe that this development model can not be replaced at present, but also our web development work is the first choice

MVCWEBAPI is suitable for mobile device interface, Mvcweb business interface display processing, this is how standard.

Why do I choose this technology portfolio?

I was the first choice of technology is very simple, from the simple development method and the study cost of personnel considerations, we all know the technical way, can overcome the development process of team personnel replacement (turnover, new)

The choice of technology is the essence of the pandemic architecture, do not use a very large underlying framework, training and learning costs are very high, from learning to development needs a long process, which is what bosses do not want to see

It also takes into account that the use of the application system is not very

So: asp. NET MVC,EF,IOC container ,easyui, layered sub -module, interface-based

MVC: currently applicable to all front-end application deployment, including website, System backend, adaptation, API interface, no mixed-type code like webform,php, separation of concerns

EF: micro-software own things, after all, very handy, updated quickly, support the mainstream database, easy to expand and change, but the shortcomings we all know, large-scale traffic system is not suitable for

At the same time, Orm obviously does not have a raw SQL statement comes more directly, but ease of use and development speed is undoubtedly

injection: inject container I chose unity in the most popular IOC injection containers, and at the time, unity was a stable type of autofac,spring.net, like the popular one, until today

After many years of version evolution, the performance of the large injection frame stability, and ease of use are similar, so regardless of the choice that is good, we achieve the same effect, and their principles are the same

Easyui: for the application system, I think the most important thing is the data table, processing and displaying the complex business model is the necessary first choice, Easyui components have everything, I wanted to change to bootstrap, but for the application system

Bootstrap is not really suitable, especially in the development of speed and display, although more lightweight, but you will end up for the interaction to scratch your own head, do not believe you can try. However, the interface published on the internet can be used

BootStrap, non-conflict, finally I still look tired of easyui skin, their efforts to write 5 sets of Easyui skin, in fact, not difficult. Portal

Layered sub-modules: from database to file naming they are normative, but also to the system of the Convention and coding norms, each company has a certain code codes, but Datong small a different, such as workflow module, flow in the database table is Flow_

As a prefix, areas in MVC for Flow,bll,dal, Flow.bll,flow.dal. This facilitates the development of rapid set-up and T4 of the unified generation, but also for the system's splitting, while our bll,dal is also applicable to

WINFORM,WPF and other desktop software, or as a WEBAPI business layer.

based on interface: norms, constraints, separation, etc., popular point I mainly as sub-package, business code hiding, team development as long as the definition of the interface, and no need for practical business, can be contracted at the same time development, very good

How to read articles in this series

Theoretically any interested park friends can understand and read, but if you have a certain amount of work experience, it seems to be more than a multiplier.

Section 1-10: The basics of getting started with this series. Basically determined from the user request to read the entire process of the database, the main explanation Easyui is how to read the background data, through the interactive way of JSON data, fast no refresh, the same applies to other front frame. such as Extjs,jqgrid and so on.

11,12,13: Is the system of the log, exception processing, the log can record the user's every action, exception can let developers quickly get problem positioning.

Section 18-28: Permissions are the most basic thing in every application system, and theory must be owned. The key permissions are the degree of control, this series controls the permissions to the button level, and processes the request through a global filter

--------------------the middle of the reading section------------------

The 58,59 section is the refactoring section of this series, with the T4 template that encapsulates the Dal,bllmodel ' duplicate code, the code generator's bll,dal is no longer needed. Greatly eliminates a lot of duplicate code, must read. Even if your system does not fall within the scope of this series, 58,59 may be helpful to you.

The follow-up will bring some webapi to open and verify, let Webapi open to the mobile end of the article, let us know how Android is communicating with our API and verifying

written in the last

Thank you for all the support, is so-called praise high urine far! Hey..

Build a backend management system for ASP. Mvc5+ef6+easyui 1.4.3+unity4.x Injection (60)-System Summary