ASP. net mvc + EasyUI permission design (1)

In the past, Wei was indeed very busy, and his Blog was basically not updated. I am very sorry, so in the future, Wei will try to take the time to write it, it may be time-consuming. Today, we will share with you some articles about permission design. Many people have already written this knowledge in the garden, therefore, Old Wei cannot give an axe to his class. He just shares his understanding and practices with you. If there is anything wrong or something that can be optimized, old Wei hopes to get your suggestions.

Permission is a required module in any project or product, which is basically provided as basic data, in order to control the access and execution permissions of each user, the permission system must be controlled. Of course, the permission system can be very simple and complex, the setting can be complex to controlling the reading and writing of a field in the table. Of course, we have to look at the specific analysis of the project, but no matter how we analyze it, the idea of permissions remains unchanged.

Regarding the concept of permission, Lao Wei will not talk about it here. You can check it online. Here, Lao Wei mainly talks about the several tasks we need to do in permission!

1. After a user logs on, the system lists the menus owned by the user based on the user's logon information.

2. After a user logs on, the system obtains the user's permissions based on the user's logon information.

3. When you log on to the module, you must determine that the user has the permission to execute the module.

These three things are very important. Undoubtedly, to achieve these three things, our permission system must authorize the user and perform other operations. Therefore, the permission system is more important.

Based on the above requirements, we can analyze the relevant data tables. For details, refer to the blog of golden ocean. Because Wei is not a complex permission system, the design of data tables is not that complicated, but the idea is the same.

This chapter is just the beginning, so it does not involve the design of data tables and the construction of projects. But here, Wei has to talk about the technology and environment required by this permission system. Old Wei plans to use ASP. net mvc + EasyUI + SQL Server. In the original plan, Old Wei was preparing to use MySql, because Old Wei had already done one in MySQL, so this time he was preparing to use SQL Server. Some netizens may ask, why not use EF? In fact, this problem is also very depressing, EF said that the Old Wei sentiment is very deep, a company project uses EF. Then it was killed. This is not to say that EF is not good, but it may be because Old Wei's understanding of EF is not so deep!

Now, let's get there today. The next article officially started to write code by Wei!