Content

When you look at sample code in MSDN, one thing quickly becomes clear: if you use an O/R mapper such as Entity Framework or NHibernate, you should pair it with the repository pattern. Ideally, you should even use generic repositories. After all, this is the only way to hide the O/R mapper of your choice from the layers above it. But is this game of hide-and-seek advantageous? How useful is it really to deliberately keep higher layers dumb? And does this approach also give you flexibility? These are precisely the questions this session will address. Using a few practical examples, we will compare the repository pattern with typical MSDN applications to see whether it really has its place.