The data mapper in Griffin.Framework have been updated to support fluent mapping and some other new features.
I got the question above in my ADO.NET done right article. I hope that my answer can help others and therefore it got this dedicated post.
I’ve created a small example project that uses the data mapper in Griffin.Framework to work with SQLite.
As you might know I’m running a .NET exception service called OneTrueError. When I moved from a NoSQL db to SQL Azure I had to be able to work with the database in some way. I’m not using OR/Ms any more. They might significantly reduce the bootstrapping, but in the long run they always tend to make you struggle as the application grow. To me, ORMs is a bit like ASP.NET WebForms, but for data. i.e. it tries to make something what it isn’t. I therefore wanted something that did not take away the control from me nor hide the underlying layer. I still want to work with my domain entities though.
This article demonstrates how you can create a Unit Of Work implementation for ADO.NET
The repository pattern has been discussed a lot lately. Especially about it’s usefulness since the introduction of OR/M libraries. This post (which is the third in a series about the data layer) aims to explain why it’s still a great choice.
ADO.NET is actually quite powerful if you use it correctly. This post will teach you everything from making your ADO.NET code driver independent to how to implement the repository pattern and unit of work. This is the follow up post of my “Datalayer, the right way” post. The purpose is to demonstrate that ADO.NET can be used as an alternative to OR/Ms.
The goal with this post is to give you a better understand about how you can design your data layer and why it’s important to create a complete abstraction layer.