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.
We have a big portal that needs user registration to allow them use its services. It’s already done in .NET and SOL Server 2005. We are in the phase now of discovering all the problems of the current registration system to build a new robust and flexible one that can be extended easily and can be more usable for all services.
What are some best practices and design patterns to rebuild this using good architectural practices?
This question is really too open ended to give a good answer to. However, I would recommend using the built-in Membership stuff: http://msdn.microsoft.com/en-us/library/tw292whz%28v=VS.100%29.aspx