Should I implement DTOs in repository pattern with EF? [closed]

Answer 1

the best way for MVC (and almost others in general) is to do EF -> DTO - > ViewModel -> View.

you should never use EF as entities bound to the View. you will shoot yourself in the foot but also defeats the purpose of MVC - your model part.

so create your EF but also then create your model which gets bound to the View. yes, seems like duplicate work but really, its not - it gives you more fine grain control one what to show or contain in your model for the view.