I originally conceived of Dapper.CX as a set of extension methods, but a service-based DI-friendly architecture probably has more appeal to devs today, and for that matter I see the value in it. I'm already doing this, see Services, but this is not well-publicized. So, I think this deserves a dedicated section on the Readme.
I originally conceived of Dapper.CX as a set of extension methods, but a service-based DI-friendly architecture probably has more appeal to devs today, and for that matter I see the value in it. I'm already doing this, see Services, but this is not well-publicized. So, I think this deserves a dedicated section on the Readme.