I totally agree. Dapper is my number one choice every time.
My first (and hopefully last) encounter with EntityFramework was back in one of it's early versions (IIRC 1.2) and it was terrible in every way. After that, I used to just build "populators" to iterate through dataReaders and populate my objects. I've only been working with Dapper for the last couple of years and I've barely scratched the surface of what it can do, but for my needs it's auto-mapping abilities is more than enough.
I think what I like most about it is what I hated most about EF - it's the fact I write my own SQL. I like SQL and I'm pretty damn good with it, if I might say so myself - and I consider that fact a great benefit over full-scale ORMs.
During my talk, I made a similar comment. I'm not amazing with SQL, but I'm pretty good for most stuff and I know how to write SQL that works well with my overall application.
With EF, it always felt like I was throwing a dart at the wall in a black box. I really like knowing what's going on, simply because I'm telling the library/framework to do it.
Thanks for the comment!
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I totally agree. Dapper is my number one choice every time.
My first (and hopefully last) encounter with EntityFramework was back in one of it's early versions (IIRC 1.2) and it was terrible in every way. After that, I used to just build "populators" to iterate through dataReaders and populate my objects. I've only been working with Dapper for the last couple of years and I've barely scratched the surface of what it can do, but for my needs it's auto-mapping abilities is more than enough.
I think what I like most about it is what I hated most about EF - it's the fact I write my own SQL. I like SQL and I'm pretty damn good with it, if I might say so myself - and I consider that fact a great benefit over full-scale ORMs.
During my talk, I made a similar comment. I'm not amazing with SQL, but I'm pretty good for most stuff and I know how to write SQL that works well with my overall application.
With EF, it always felt like I was throwing a dart at the wall in a black box. I really like knowing what's going on, simply because I'm telling the library/framework to do it.
Thanks for the comment!