Home/ Questions/Q 895791
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-15T14:36:59+00:00

I’m going to use Entity Framework 4 in sort of big project. And i

  • 0

I’m going to use Entity Framework 4 in sort of big project.

And i know that many professional programmers advice to depend on my business classes instead of EF Model classes.

Actually there is sound inside my brain tell me “Don’t depend on that generated classes !. Just make your hand dirty with your stuff don’t let someone else do that for you. !!”

But actually i don’t know where is the problem to use these generated classes in such a big “Enterprise” projects.

So please make me understand why ???

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    There’s absolutely nothing wrong using the EF-generated classes. That’s what they’re there for.

    But if you misapply the technology, you are in for a lot of problems. For example, a lot of beginners will try to use those EF-generated classes for everything. They’ll take the classes, marshal them across an AppDomain boundary with WCF or Remoting, and maybe they’ll bind to them on their front ends. That might work for a quick and dirty CRUD-based application, but it’s not going to fly for anything with any real size.

    Why not? Because EF-generated classes are modeled in the data “domain” of your application, not the presentation “domain”. What a user might want to interact with is often not an object which is 1:1 with a table in your database. For example, a user might have a grid of “Products”. Inside this grid would be the total dollars sold of the product, along with certain indicative data about the product. While the indicative data (Name, Size, etc) will probably come right off the Product table and therefore the generated Product class from EF, the aggregate data (total dollars sold) is an aggregate value.

    What we typically do is use the EF-generated classes in our service, and then use the service to translate the EF classes into ViewModels which we then bind to on our front ends using WPF (or whatever your favorite technology is). That gives us the separation of concerns we’re looking for.

    • 0