to use or not to use membership (in asp.net 2.0?)

[Steve]

I really want to have my own user database table, customized in my own
way, with custom relationships to other tables?

1. Should I in that case forget all about the new membership features
in asp.net 2.0, and just write my own code?

2. Would I also be forfeiting the new personlization features, i.e.
profiles?

 

[Juan T. Llibre]

re:

1. Should I in that case forget all about the new membership
features in asp.net 2.0, and just write my own code?

If you can do that...more power to you.

re:

2. Would I also be forfeiting the new personlization
features, i.e. profiles?

Why wouldn't you include the profile tables in your new db ?

What I'd do is *start* with the aspnetdb provided,
and then *add* the features you want to add.

You'll wind up with a superset of the default features.



Juan T. Llibre, ASP.NET MVP
ASP.NET FAQ : http://asp.net.do/faq/
Foros de ASP.NET en Español : http://asp.net.do/foros/
======================================

 

[Patrice]

AFAIK it's based on "providers" i.e. you could implement your own so that it
uses your own data structures...

See : http://msdn2.microsoft.com/en-us/library/f1kyba5e(en-us,vs.80).aspx
(Implementing a Membership Provider)

So you'll have to write your own code but you can still benefit from those
built-in capabilities. This is a general behavior. Even resources could use
your own provider to read resources from whatever you want instead of the
standard resource files...