Introduction to MVC architecture-Framework Layering

Example products based on the ASP. NET MVC 5.0 Framework, Source: Http://www.jinhusns.com/Products/Download

Tunynet.infrastructurs is our own encapsulation of a low-level DLL infrastructure, we only need to reference this DLL outside to call the inside of the method to complete the implementation of the outside function

This is mainly in the cache models, mail, Di container, event, attachment management, image processing, kvstore, Logging, physical encapsulation, data access, timed tasks encapsulated some utilities, such as page truncation of the encryption, decryption and other packaging

Modules reference our bottom tunynet.infrastructurs to accomplish some of the common functions of the implementation of the domain layer
Modules There are areas, top-stepping, @ Users, categories, collections, concerns, list notifications, permissions, recommend these commonly used components

Core references Modules and tunynet.infrastructurs to complete a large, commonly used application component, such as information, comments, counts, attachments, etc.

Presentation is primarily for the previous segment of the package, such as Html.helper extension, page header output, routing settings, partition management, page addressing and other management

The Web is primarily about interacting with the user, presenting the page to the user

Background view needs to be placed in the consoleviews, the background of the route using area and areaname for consolelviews;
When the foreground switches between different theme, it needs to be set in <appSettings/>, theme defaults to default.

From the top down, the elements in the layer depend only on the layer or its underlying elements, not on the upper level.

Introduction to MVC architecture-Framework layering