Have you come across database connection overrun due to developers forgeting to close db connections? 'Easy-Data-Access' is a simple framework that solves the issue. It also helps well designing your data layer with boosted developer productivity.
At the very first glance, I sensed a good design and a highly confident architect here, then I peeped in to see how good this design/ the architect is.. Having accepted the fact that the design is simple and quite good for the type of problem you guys were trying to solve at the time, let me also highlight a point I noticed that I don't like about your design.. In your design, I see you letting one of the most important design decisions float at developer desecration, which is bad.. Let me explain it for you.. The generic 'CommandBase' is forced for its derived class to implement the 'Body' method, hence the architect of the 'CommandBase' have forced the poor developer to decide on how to build the 'DbCommand' for it. I thought it is very poor.. In your Test, you quite correctly use the 'AddParamenter' method avoiding 'SQL Injection' to add required parameters, but how you guaranties that a developer would do the same?? What would be the fate of your system if one of your weak developers decides to directly append the parameters to your sql command.. won't your system be a easy target for inexperience hackers... ?? I thought your design could have improve little more to avoid it. What do you think?