Is it a bad practice using model classes in controller in mvc?

Question

I wanted to compare with best practices when working with an ORM or database tables in asp.net mvc. One of the major questions I have is should I instantiate

Answer 1

Yes, by practice. You should keep controller as skinny as possible and separate each concerns.