I am using Entity Framework to connect to MS SQL (Azure). I have a WPF application, and I am using MVVM. But...where is my Model layer? Right now I have made the 'traditional' Model layer, which then translates the Entity Framework into new objects. That
works, - but I am missing out of all the implicit benefit of Entity Framework! If I pulled a collection directly from the Entity Framework to the the ViewModel, I could then work on the collection (add, delete, update) and then just run SaveChanges() on the
connection and it was a done deal. But right now it is the object in the Model layer that I work on, and then in this object I have to add, delete or update another object in the database through Entity Framework.
To get the benefits, should I just skip all the extra objects in my Model layer and make the Entity Framework a part of the Model Layer (although it is also a data access layer, of sorts)? Or is there a way to pass the Entity Framework objects through the
Model layer smoothly so I still maintain the wonderful SaveChanges() functionality?
View Complete Post