I don't know of a specific example combining the EF technology with the MVVM pattern, however...

Entity Framework would really not "intersect" with MVVM code, in any tangible way. The EF code is really all tied to the Model in M-V-VM. MVVM is about interaction between the model and "other layers", in this case, the View (for presentation) and the ViewModel (for control).

Since the EF code is really entirely in the model, and not part of the visual representation of that model, it's a separate issue. You should be able to use any MVVM article for discussion of MVVM, and any EF article for learning about EF. EF is all within the Model, so there shouldn't be too much confusion.

However, there are some really great nuggets of wisdom in this alt.net discussion , in particular, read Glenn Block's responses. He gives some valuable guidance, and some specifics on why you don't want to let the EF code "pollute" your ViewModel (basically, keep EF in the Model, not the View/ViewModel).

---

Reed Copsey, Jr. - http://reedcopsey.com