Open GoogleCodeExporter opened 8 years ago
I would even say that given how small, simple and useful the SqlBuilder is, it
should be included inside the same Nuget package as Dapper itself.
The argument here is that I don't like having tons of assembly references, it
even gets more ridiculous when those assemblies only contain 1 (public) class.
I'd prefer a single assembly, even if it includes a (tiny) bit of fat that I'm
not going to use.
If people wanted to go as lean as possible, they would include Dapper in their
project at the source level anyway.
Original comment by joel.du...@gmail.com
on 5 Jul 2012 at 5:36
Looks like there is a Dapper.Contrib, but it hasn't been deployed in who knows
how long.
Original comment by cpf...@valetude.com
on 21 Jan 2014 at 6:14
Original issue reported on code.google.com by
kjwar...@gmail.com
on 25 Jan 2012 at 12:31