Establish a standard routine with the. Net 2.0 Membership Function (a) primer + trailer

Since the last update blog has been 8 months now, a small information collection project has been canceled, so here to remove the big pit first.

But the last project made me notice that the. NET membership feature that was originally intended to be used in the information acquisition project is quite rich. With simple built-in objects and configuration tools, we can clearly and conveniently build a very easy to expand user management function for many of our small projects. Actually I have done a lot of OA MIS system is the user Rights Management module is the most waste of time, with this system, I really have a bit of peace of sleep.

If you see here you have no clear concept of membership, please open your vs2k5 to see a website Engineering toolbar

"Isn't that some of the weird landing controls that can't be used?"

Yes, if you haven't used the membership function. The events, properties, and methods provided by these controls are almost completely unusable, and it is baffling.

In fact, they are very useful, they are a complete set of m$ provided by the basic face members. The so-called wasted deep like the sea, you see them these controls are not insignificant, but you can not imagine how much trouble behind the package, and we use how simple Oh @_@

First, draw a simple structure diagram

As shown in the picture we actually call this system membership, just because the basic part of the system, the basic class of management users is called membership, The entire landing plan is actually System.Web.Security the entire namespace to support, in fact, is called the. NET 2.0 Web security solution. Of course the custom has been established (our rookie is easy to be superficial puzzled, so we agreed first-B)

The following sections I'll start with how to configure membership to customize ObjectDataSource Management membership \roles \profile