c# - Entity Framework 6 on MVVM + PRISM patterns -
What is the better way to use unit framework with PRISM, MVVM and (Business Layer)? We will have time to learn and apply (C #) 300 entities.
I had seen something about using Prism's Di together with EF, POCO (CodeFirst) directily, ModelFirst ...
I have prism, MVVM, EF and DI There is not much experience with, only a little theory.
What is the best arbitrator to do this?
If I correctly understand the question, then you've got a presentation based on Prism architecture and business layers. And you consider the Entity Framework as a data access layer.
Architecture
The title of the best course available at PluralSite is the course of the unit's architecture in enterprise-level applications that discusses best practices in terms of infers large sets of data.
The EE is contained in the data layer, but business layers should depend on the stock / unit of the work layer. The summary of the repository layer is encrypting unnecessary data access codes actions such as receiving repostitory (GetCustomerById, GetAllCustomers), Add (AddCustomer), RemoveCustomer, Send (SendToDatabase). The code is the first of the latest approach and I would recommend it. The comprehensive dissertation you can find on the topic on stackoverflow. Domain Driven Design (DDD) is a pattern that helps manage the large set of entities. It supports the separation of concerns and read more about it. See the presentation that initially shows the unit framework and DDD. approach
Domain Driven Design
Comments
Post a Comment