Nop (1)

ArticleDirectory

• Those projects in the \ plugins \ Folder
• \ Presentation \ NOP. Admin
• \ Presentation \ NOP. Web
• \ Presentation \ NOP. Web. Framework
• \ Test \ NOP. Core. Tests
• \ Test \ NOP. Data. Tests
• \ Test \ NOP. Services. Tests
• \ Test \ NOP. Tests

I have always wanted to learn about NOP design, but I didn't spare time. Some cool people have analyzed this in the courtyard. Here, kaibo learns the knowledge they have summarized, and aims to digest and absorb it by themselves.

Write your understanding of Nop from today.

The following is a transfer to the yard:

\ Libraries \ NOP. Core
The NOP. Core Project contains a series of core classes of nopcommerce, such as cache, events, helper classes, and business objects (such as order and customer entity classes)
\ Libraries \ NOP. Data
The NOP. Data project contains a series of data types and methods to read and save data from databases or other data media. It also helps to separate the data access logic from your business objects. Nopcommerce uses the Entity Framework (EF) code-first method, allowing youCodeDefine entities (all core entity classes are defined in NOP. Core), and then let EF generate a database, which is why code-first is called. You can use LINQ to query objects. It converts queries to SQL statements and runs them in the database. Nopcommerce has a cool B API that allows you to fully customize persistent mappings. Here you can find code-first materials.
\ Libraries \ NOP. Services
This project contains a series of core services, business logic, verification, and data computing methods, that is, the legendary business access layer (BAL)

Those projects in the \ plugins \ Folder

Plugins is the solution folder of Vs, which is in the root directory of your solution on the hard disk. Because the input path of the project during compilation is ".. \.. \ presentation \ NOP. WEB \ plugins \ {group }. {name} \ ", so that the plug-in dll will be automatically placed in \ presentation \ NOP. WEB \ plugins \ folder to place deployed plug-ins. In this way, the plug-in can contain static files such as CSS or JS, so you do not need to copy these files between projects.

\ Presentation \ NOP. Admin

Nop. Admin is an MVC project. If you have never used ASP. net mvc, Click here for more information. You may have guessed that this is the management background in the presentation layer. You can find it in the \ presentation \ NOP. web \ administration folder, and this project cannot run.

\ Presentation \ NOP. Web

Nop. Web is also an MVC project, the presentation layer of the front-end online shop. This is the project you really want to run, and it is also the whole application.Program.

\ Presentation \ NOP. Web. Framework

Nop. Web. Framework is a class library project of the presentation layer, including some shared presentation functions that can be used by the backend and foreground.

\ Test \ NOP. Core. Tests

Nop. Core. tests is a test project of Nop. Core.

\ Test \ NOP. Data. Tests

Nop. Data. tests is a test project of Nop. Data.

\ Test \ NOP. Services. Tests

Nop. Services. tests is a test project of Nop. Services.

\ Test \ NOP. Tests

Nop. tests is a class library that contains a common class and auxiliary method used in other test projects. This project does not contain any test cases.