asp.net membership provider api. usability. best-practice
Posted
by Andrew Florko
on Stack Overflow
See other posts from Stack Overflow
or by Andrew Florko
Published on 2010-05-10T20:11:38Z
Indexed on
2010/05/10
20:14 UTC
Read the original article
Hit count: 277
ASP.NET
|membership-provider
Hello everybody,
Membership/Role/Profile providers API appeared in early days of asp.net
Nearly everytime I can't live with standard API & have to add some extra functionality (for sorting, retrieving e.t.c.). I also have to use different database structure often (with foreign key to some tables for example) or think about performance improvements.
These considerations forced teams I took part in to build own providers but I can't stand to implement providers API (because we don't use 70% of standard functionality at least). Moreover, providers that were built for exact projects were rarely reused.
I wonder if someone found swiss-knife early-days-API providers implementation that is usefull for any kind of project without refactoring... Or do you use your own implementations of early-days-API's Or may be you abandon standard architecture and use lightweight implementations ?
Thank you in advance
© Stack Overflow or respective owner