Ef and Dapper.net in a single package

dapper entity-framework

Question

Is there a reason my solution couldn't use both EF and Dapper.NET? Due to the programming's flexibility, EF prefers to use, but when I need to choose numerous huge quantities of data, I use the Dapper. Can it result in any disputes?

1
1
3/5/2015 7:25:38 AM

Accepted Answer

You should be alright as long as you don't cross the waterways. In reality, I utilize many tools; use EF when you want to use EF's core functionality and dapper when you need easier data access and are more concerned with speed than complexity / flexibility. Projects often fail because a single tool is forced to do tasks at which it does not excel "because we employ Tool X."

3
3/4/2015 3:53:59 PM


Related Questions





Related

Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow
Licensed under: CC-BY-SA with attribution
Not affiliated with Stack Overflow