I have two question about working with dapper:
-
Is there any way to load navigation key property like entity-framework (lazy-loading)?
-
What’s difference between
POCO serializationanddynamic serialization?
which is better? and how can I use this serialization?
No, Dapper is a direct-SQL library, and that’s why it’s so ridiculously fast. There is no overhead surrounding automated loading. You can however load more than one entity at once.
POCO serialization is more efficient because the type is well known at compile time, dynamic serialization is a bit more expensive because it has to be evaluated at run-time. Other than that there isn’t really a difference.
However, I would recommend Dapper above all other libraries anywhere. It’s simple, fast, and extremely flexible. And believe me, I’ve used a lot of frameworks and libraries for data access.
Dapper Documentation
Have a look at Multi Mapping and Multiple Results