O'Reilly logo

Fluent Entity Framework by Rebecca M. Riordan

Stay ahead with the world's most comprehensive technology and business learning platform.

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, tutorials, and more.

Start Free Trial

No credit card required

The proof of the pudding...

So far we’ve looked at the difference between relational database design and OOA&D in terms of how we think about the problem space. That’s important, of course, but in a real application you’ll probably spend more time using the model than you will building the model. So let’s end this chapter with a quick look at navigating an ADO.NET data model versus the kind of model you can build using Entity Framework. I think you’ll agree that easy things are easy in both, but tricky things start getting very tricky very fast in ADO.NET.

To access an entity

ADO.NET uses a DataSet to contain all the tables that represent entities; Entity Framework uses a DataContext. The only difference conceptually is that the DataContext

With Safari, you learn the way you learn best. Get unlimited access to videos, live online training, learning paths, books, interactive tutorials, and more.

Start Free Trial

No credit card required