Re: Membership when more info is needed for a User
- From: "sloan" <sloan@xxxxxxxxx>
- Date: Wed, 16 Jul 2008 13:03:26 -0400
You should look first at the Profile to see if its enough to help you.
http://odetocode.com/Articles/440.aspx
If you're using SqlServer, you ~can~ inherit from
SQLMembershipProvider.
Not everyone uses sql server obviously.
"Savvoulidis Iordanis" <SavvoulidisIordanis@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote
in message news:E4BAD51A-C1E0-40A9-B4B6-2E660C827090@xxxxxxxxxxxxxxxx
I use SQL Server Membership provider and my data are also stored in SQL
Server. But the default user fields are not enough for my users info. So I
created another Users table apart from aspnet_Membership. It has a
PK(uniqueidentifier) to create the reference to aspnet_Membership table
and
my other info columns.
Having read about the Custom Membership Provider in .NET help, it says
that
I should create a new object inherited from MembershipProvider and rewrite
all of its methods so it can be used by the membership system calls.
The question is:
Why not inherit from SQLMembershipProvider instead of MembershipProvider?
That way, most of the methods are already implemented and the only thing I
would do is to override the CreateUser, UpdateUser, GetUser methods, that
is,
only a few
. In the 1st line of the overriden methods, I could use Mybase.CreateUser,
Mybase.UpdateUser and so on, and just add the rest of the stuff I want to
do
to deal with my extra info.
Am i in the right direction? I'd like a comment.
TIA
Iordanis
.
- Prev by Date: Re: Sort files in a directory
- Next by Date: Cross Browser and Validation in VS 2005.
- Previous by thread: Forms Authentication vs MembershipProvider
- Next by thread: Re: Membership when more info is needed for a User
- Index(es):
Relevant Pages
|
