Starting with. NET 2.0, ASP.net has entered a period of advocacy for less-than-write code-Multiple configurations
"The machine is advanced, we just have to drive the pig in and the sausage comes out of the conveyor belt." ”
Here's the job of starting the machine and catching the pig.
Before we catch a pig, let's take a look at the approximate way web.security works.
When a page opens the system will first read the system.web according to the configuration segment in the process to establish the corresponding various provider instances.
All subsequent login controls automatically invoke the methods and properties of the corresponding provider instance when interacting. So most of the work is done in the configuration.
Component part of the object there are many peers who recommend themselves to write lest too dependent on aspnetdb specific can refer to Fantasia articles
But this is a standard routine, so it's time to build on the m$ standard base
The specific configuration is as follows
1 configuration database
Running \windows\microsoft.net\framework\v2.0.50727 under the Aspnet_regsql.exe