Re: ASP.NET Membership - Changing the contract

Hi,

there are no such links - also for profile - you will not lose the profile functionality - you may need your own provider - but thats another story.

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

The "links" I'm referring to are posible collaboration between the
Membership and other features of VS2005 that might be interesting to
maintain.  I don't know if there is any feature in VS2005 that
utilizes the Membership API under the covers, if there is any, I'll
like to know it.

For example, if you use the Profile feature, then, there is
functionality that you can use with Binding, if you decide to
implement Profile type functionality yourself with your own objects,
then you lose that functionality in the Binding side.  This is just an
example, I wonder if there are features like that in VS2005 that I'm
going to lose if I create my own Authentication/User mgmt library.
Please advise.

If there is nothing to lose besides the Membership itselft, I'll
rather do my own.

Thanks

"Dominick Baier [DevelopMentor]" wrote:

Hi,

i don't know about which "links" you are talking.

If neither the provider interface nor the controls fit your needs -
why do you want to use the provider pattern - it will be more work
teaching the provider your new tricks than writing your own
authentication/user mgmt library - you have to do that anyways if you
write a provider.

my 2c

---------------------------------------
Dominick Baier - DevelopMentor
http://www.leastprivilege.com

I want to create a custom provider, that is going to work with an
existing database (I'm not going to use the aspnetdb).  I'm going to
need to provide additional fields in the creation of a new user
account, new fields for changing password and also new fields for
the login.

Let's take the MembershipUser as a sample, I know that I would need
to inherit from MembershipUser and add my custom fields, what's
going to happen with the UserControls?  How am I going to pass the
new fields to my new extended object?

The reason of using the Membership is because I have the feeling
that there is "collaboration" with other new features in VS2005, if
I don't use the Membership, I feel that I'm going to loose more than
just the Membership.  To make an educated decision, anybody knows
what are the "links" between the Membership and other features in
VS2005, if any?

Any good advice to approach my problem besides create my own?  I'm
also willing to create my own UI layer and just implement the
Provider, but wish there is a way to reuse the existing Membership
UserControls as much as I can if it makes sense.

Thanks



.

Relevant Pages

  • news from http://www.bikejournal.com
    ... Basic membership is free. ... Create as many filters ... Plans are underway for a major upgrade to bikejournal. ... and new features will be added periodically. ...
    (rec.bicycles.misc)
  • Re: the membership of asp.net2.0 is useful in my case?
    ... Its not a matter of like or dislike. ... > membership or profile). ... > Profile provider that works with all the UI controls just the same as the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How to integrate Profile with Membership
    ... Exactly -- Profile and Membership are two related, but different features. ... Think of them are two different storage locations for different types of data. ... Both types of data are for the one person, but one set is for authentication and the other is for the extra profile data. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: the membership of asp.net2.0 is useful in my case?
    ... It'd be nice to have these documented, but on the other hand that's somewhat going against the idea of a provider (wether it be membership or profile). ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: MembershipProvider limit no effect.
    ... Dose we need implement these features in my custom Membership provider or ... Juan T. Llibre, asp.net MVP ... or password answer of a membership user. ...
    (microsoft.public.dotnet.framework.aspnet)