ASP. NET MVC +easyui permission design (i)

In the previous period, the old Wei is really busy, blog basically did not update, very sorry, then in the back of the time, the old Wei will try to draw time to write, may not be too rich in time. Today, the old Wei and everyone to share about the rights of the design of the article, because in the garden has been a lot of people have written this knowledge, so old Wei here can not swim, just to their understanding and practice and share with you, if there is something wrong or can be optimized place, Old Wei very much hope to get everyone's advice.

Say permission is in any project or product must be used in the module, and this part is basically as the basic data to provide, in order to be able to control the individual user access and execution permissions, need permission system to control, of course, the permission system can do very simple can also be very complex, Settings can be complex to read and write to a field in a table. Of course, these will have to look at the specific analysis of the project, but no matter how the analysis, the idea of authority is unchanged.

About the concept of permissions, Old Wei here is not more said, we can check on the Internet, here old Wei mainly to say a few things in the authority we want to do!

1, when the user login, the system according to the user login information, you can enumerate the user's own menu

2, when the user login, the system according to the user login information, you can get the user's permissions

3, when the user login, access to the module, you need to determine the user in this module when the implementation of the relevant permissions.

These 3 things, can be said to be very important, undoubtedly to achieve these three points, our permission system must be authorized for the user, and so on, so the authority system is more important.

According to the above requirements, we can analyze the relevant data sheet, specific people can refer to the "Golden Ocean" blog, said very detailed. Because Old Wei here is not to do a complex permission system, so the design of the data table is not so complicated, but the idea is the same.

This chapter is only a beginning, so there is no data sheet design and project construction, but here old Weide said the authority system adopted the technology and needs of the environment. Old Wei intends to use ASP. NET Mvc+easyui+sql server to do. In the original plan, old Wei ready to use MySQL, because the old Wei in MySQL has already done one, so this time ready to use SQL Server. Perhaps some netizens will ask, why not use EF? In fact, this problem old Wei is also very depressed, EF said the old Wei sentimental very deep ah, the company a project with EF. It was later aborted. This is not to say that EF is not good, no, but may be old Wei's understanding of EF is not so deep!

OK, let's go here today, the next chapter of Old Wei formally began to write code!