As a data-access technology designed to meet the needs of a variety of development styles, the Microsoft Entity Framework presents developers with a lot of options. Some of these choices need to be made early on in your development cycle and will impact what options you’ll have further along in your development process. In my next three columns, I’ll provide high-level guidance for some of the biggest decisions you’ll need to make with the Entity Framework:
Code First, Model First or Database First workflows for creating a conceptual model Lazy, explicit or eager loading Plain Old C# Objects (POCOs) or EntityObjects LINQ to Entities or Entity SQL
There are many more design decisions to be made throughout your application, but these questions are the most frequently asked—and often debated—by developers as they begin to implement the Entity Framework into existing or new applications.
I’ll attack the conceptual model creation workflow here and cover the other three topics in the next two columns. My goal is to provide a high-level overview...