Ef and Dapper.net in a single package

dapper entity-framework

Question

Is there a reason why I couldn't use both EF and Dapper.NET in my solution?? EF like to use due to the flexibility of the programming , but when I need to select several large amounts of data then used the Dapper. Can it lead to any conflict???

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

Accepted Answer

As long as you don't cross the streams, you should be fine. In fact, I strongly suggest using more than one tool; use EF when you want to use features that are key to EF, and dapper when you need simpler data access and care more about performance than complexity / flexibility. Forcing a single tool to do things it doesn't excel "because we use Tool X" is usually where projects go wrong.

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