Why don't you use the membership provider and tables?

Feb 1, 2009 at 12:24 AM
Well the question says it all?  Was wondering why you don't use the aspnet_user and other tables.  Also, when registering, if the email fails to be delivered, the user will never be able to log in
and also can't retrieve their password.
Feb 4, 2009 at 3:59 AM
ASP.NET Membership has a long tail which I like to avoid. Yes we need to add a functionality to resend the activation link.
Feb 6, 2009 at 1:47 PM
Maybe it has a long tail, but it works out of the box and shouldn't be something we have to re-think in each new application.  Also it used in so many applications, I hate to have two code-bases doing the same thing.  Furthermore, if I integrate kigg into another application that already uses the membership api, it makes it very awkward.  Perhaps you could expose an API so that shared sign-on is possible.  For me this is really critical.
Feb 6, 2009 at 4:07 PM
Pls consider that It has OpenID which requires so many hack in ASP.NET Membership to make it functional. I do need to rethink whether it is at all possible.
Jul 1, 2009 at 9:12 PM
Edited Jul 1, 2009 at 9:12 PM

Any update on this?