Stop using Entity Framework as a DTO provider!

Entity Framework is a great tool to retrieve your data from the database. However, it is also a bit complicated, and requires that you read a bit more than just the "Getting Started with EF" page. Unfortunately, this seems to be what most developers do.

Database

.NET

At least I think that is why I keep seeing people using it to replicating the database structure in their code with DTO:s. This is not the way it was intended to be used. It was intended to persist and retrieve data for you C# object. Not just DTO:s.

And if one more person tells me "we used a micro-ORM for this project, since it does the same thing as EF but without the complexity", I will blow a gasket!

Why not join me, Chris Klug, for a look at how we can do better? In this talk, I will show you how we can use proper OOP and still use EF to persist and retrieve our objects.

Chris Klug

Chris Klug is a developer badass-as-a-service that either creates or solves problems depending on who you ask. He loves creating and building things. Whether it be a new application, a new kitchen or a new RC helicopter, you will see him building things all the time. Most of the time, that means writing code and solving problems for clients at a company called Active Solution in Stockholm though. Except for the many days he spends at conferences and usergroups, talking about doing things he is passionate about, and for the days he goes mountain biking, IPSC shooting, kiteboarding or RC helicopter flying.
For the last 15-something years, he has been solving problems for customers, and loving it. But if he gets to choose, he'll go to the beach and kitesurf every day!