Was wandering if anyone uses ASP .NET membership? If you do, tell me what you think about it.
If you don’t use it, Are you planning to use it on future projects? If not, why?
RWendi
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Was wandering if anyone uses ASP .NET membership? If you do, tell me what you think about it.
If you don’t use it, Are you planning to use it on future projects? If not, why?
RWendi
Yes. Have used it quite a lot, and it will save you a lot of work.
There are some pain points like changing usernames, and administrative reset of passwords, that clients will often ask for, and you will have to hack your way around them.
The role provider is also pretty handy, and there are a lot of prebuilt controls that work with it, although recently hit a bug between role manager and aspnet ajax that has been a PITA.
The model is generally very good, even if you have shop around for some different providers that suit your needs.
Overall, it’s not perfect, but if you can live with it and work around it’s issues, it will save you heaps of code.
For some situations, it is maybe using a chainsaw when a butter knife would do, but it’s there, it works, and there are plenty of other people using it.
Its one kind of hammer, for the price, is ok, but there is no golden hammer.