ViewModels, Repositories, Dependency Injection, Auto Mapper
On the web there are lots of tutorials about View Models, Repositories, and Dependency Injection... some are good but none are comprehensive.
Some questions that could be answered in an upcoming tutorial... How do repositories, View Models, and DI work together? When is dependency injection necessary? When is using Auto Mapper necessary?
I like that MVC is open source and that the community is developing tools tools for making powerful web apps. Installing some apps like Ninject and Auto Mapper seem to be standard operating procedure for many developers however, there seems to be a limited number of resources that tie these plugins and design patterns and some of the powerful features of MVC together.
It is very well organized and coherent resource.
Stilgar Naib commented
It is simple people. Do not implement repositories and watch all your problems magically disappear and everything starting to make sense again.
Note that the advice against repositories only applies if you are using an ORM like Entity Framework.
I am working on an ASP.NET MVC 5 Application and had problems related to Repositories and automapper. for example the best practices? Another interesting thing would be to see how we can use tools like auto mapper to handle complex data such as , files or multiple joins on tables.
Couldn't agree more!