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.
So I’m trying to create an MVC3 web app. I decided to use EF taking care of my database first, instead of using the code first or model first approach.
So, in terms of membership, is it good practice to use the auto-generated ASPNETDB.MDF going forward, and mapping my EF database to it? Or should I scrap it and add membership to my EF database?
The membership system is well known, tested, and functions well. You should use it, unless you have a good reason not to. Even then, you still should use the base IPrincipal and IIdentity functions that Membership and FormsAuth implement.