linq - If Entity Framework is meant to work with POCOs, then why the dependency on IObjectSet? -


I'm hearing about EF 4.0, POCO, IOBJet, UnitofOffwer (By the way, UOW less than 17 years old I have heard it before) etc.

So some people talk about the repository "pattern" etc. Many bloggers are performing a "cover" or a repository or similar similar concoction, but they all require IObjectSets (or in some cases - IQueryables) so that they can close their POCOs. Hope you can write questions against them.

So if anyone needs iobagets and does not need just ILIT or any other simple collection, then we are saying that it is free from POCO and EF?

If I want to swap EF from the bottom, then I need to make sure that my "other" O / R Mapper (I know I know .. EF is not just O / R Mapper ) IObjectSet understands and can be able to parse, draw conclusions from expression questions and otherwise behave like EF. IObjectSet does not have an interface that makes POCO a unit, it is just the strong container IObjectSet. Poko means to prevent you from receiving your model squares by EF type, which offers a T4 POCO template in EF4.

The repository pattern is an optional extra layer from your ORM, which allow easy implementation of each other when needed from your ORM. Separation of concerns etc.


Comments

Popular posts from this blog

Eclipse CDT variable colors in editor -

AJAX doesn't send POST query -

wpf - Custom Message Box Advice -