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.
I have two design options to go ahead with when using MVC and NHibernate
Create a class that NHibernate uses to map to the database and create a separate class that MVC uses as the Model that the Controller passes back and forward to the view. Obviously there needs to be some data transfer methods between the two.
Use one class for both task and thus reduce the amount of code.
What is the best design method
In terms of best practices definitely and without absolutely any doubt: number 1. The something that maps is called AutoMapper and the separate class you are talking about is called view model.