Creating a Custom Membership Provider
- From: "Ryan" <Tyveil@xxxxxxxxxxxxxxxxx>
- Date: Mon, 26 Jun 2006 08:34:14 -0500
I'm referring to this Microsoft article in regards to creating a custom
membership provider:
http://msdn2.microsoft.com/en-us/library/ms366730(d=ide).aspx
I'm in the process of creating my own membership provider and just want to
make sure I get everything set up correctly with regards to the custom data
I need to store on each user. In this article, the membership provider is
inherited and all the methods are recreated to work with the custom
provider. Is that all really nessessary? I have my membership provider set
up and everything works (as far as logging in, etc.). Why not just add all
your custom fields to the existing aspnet_membership table?
Also in the above article, the only difference as far as fields in the table
are 2 new fields; isSubscriber (boolean) and CustomerID (string). So to me
it looks like it is intended that a 3rd table will be created to store user
information (in addition to aspnet_membership and aspnet_users) and the
CustomerID is a Foreign Key for this table. If that is the case why is the
field isSubscriber not stored in the new Customer table rather than the
aspnet_membership table?
Any information in addition to this one article about setting up custom
Membership would be helpful.
Thanks,
Ryan
.
- Follow-Ups:
- RE: Creating a Custom Membership Provider
- From: Luke Zhang [MSFT]
- RE: Creating a Custom Membership Provider
- Prev by Date: Re: Application pool security
- Next by Date: Re: Problem in Accessing Active Directory from ASP.net
- Previous by thread: Application pool security
- Next by thread: RE: Creating a Custom Membership Provider
- Index(es):
Relevant Pages
|
|
