asp.net mvc module wise approach or different controller and repository for each table approach is better?
asp.net mvc module wise approach or different controller and repository for each table approach
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.
asp.net mvc module wise approach or different controller and repository for each table approach is better?
Could you elaborate on your question? I think I understand… I like creating a repository for each table in a LINQ-to-SQL or entities model, for instance. I think that helps group together related logic.
HTH.