Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

7
  • You seem to think a lot of your little "innovation," but how is this any different than, say, ExecuteStoreQuery or ExecuteStoreCommand in Entity Framework? Commented May 27, 2016 at 14:02
  • I'm not getting into the EF or SQL debate. My thing is for folk who want to use SQL. So as a way of executing SQL, ExecuteStoreQuery() will fill your POCOs for you, but you still need to define your POCOs, by the look of things? And it does nothing to help you put the sql in a file, or create your parameters. Your query is not discoverable in code, or testable. Deleting columns will not produce compile errors in your application. I could go on, but I fear I'm repeating myself :-) Perhaps you could take 3mins to watch the youtube video. It's in French, turn the sound down ! English coming. Commented May 27, 2016 at 14:20
  • EF is quite capable of generating all of the POCOs automatically. What am I missing here? The real innovation of Dapper and Massive is that you don't need POCO's at all; you can just use dynamic. Commented May 27, 2016 at 14:26
  • I know almost nothing about EF. ExecuteStoreQuery() will fill an entity. Will it generate an entity from the query. Entities are generated from DB objects (or vice versa), not from queries. If your query doesn't correspond to an existing entity, you have to write your POCO, no? Commented May 27, 2016 at 14:30
  • 1
    :-) must say I'm gettin sensitive to charges of advertising when I'm putting my best idea freely out there. Here's my latest bit of aggressive commercialism. By the 3 minute mark, you should know if I'm onto something or not. Commented Mar 4, 2017 at 11:28