Introduction to MVC Architecture-framework hierarchy, mvc Architecture framework hierarchy

Introduction to MVC Architecture-framework hierarchy, mvc Architecture framework hierarchy

 

Instance product based on asp.net mvc 5.0 framework, source code: http://www.jinhusns.com/Products/Download

Tunynet. Infrastructurs is an underlying DLL infrastructure encapsulated by us. We only need to reference this DLL to call the methods in it to implement the functions of the outside.

It encapsulates some Utilities for cached Models, emails, Di containers, events, attachment management, image processing, Kvstore, Logging, entity encapsulation, data access, and scheduled tasks, for example, some encapsulation such as page truncation encryption and decryption

Modules references our bottom-layer Tunynet. Infrastructurs to implement the domain layer of common functions.
Modules contains common components such as area, top step, @ user, category, favorites, follow, list notification, permission, and recommendation.

Core references Modules and Tunynet. Infrastructurs to complete a large common application component, such as information, comments, counts, attachments, and other common applications.

Presentation is mainly used to encapsulate the previous sections, such as Html. helper extension, page header output, route settings, partition management, page addressing, etc.

Web is mainly used to interact with users and present pages for users.

The background View must be placed in ConsoleViews. The background routing uses Area and the AreaName is ConsolelViews;
When switching different theme on the foreground, you need to set it in <receivettings/>. The default value of theme is default.

From top to bottom, the elements in the layer only depend on the elements of the current layer or its lower layer, rather than the upper layer.