Request to change package name from Dapper.Common

[mgravell]

The name "Dapper.Common" suggests that this library is a core/shared/common component affiliated with "Dapper", i.e. an official part of the Dapper library. Since this is not the case, I believe that the name "Dapper.Common" is misleading and confusing.

I am requesting that you consider an alternative name, perhaps focusing on what is new/different/special about your project. Perhaps something that highlights the LINQ nature of your work? I'm not convinced that it even needs to call out the "Dapper" part - from the API, it seems that Dapper existing underneath is an implementation detail that shouldn't concern the consumer.

[soul-soft]

What do you think of "Dapper. Linq"? Will dapper better support anonymous types?

[soul-soft]

Good advice. I'll decide to use "dapper. linq"

[mgravell]

Will dapper better support anonymous types?

You've logged an issue about it, and I'll have a look at it. Right now, I genuinely don't know, as until I look: I don't know what possible edge-cases and complications I'm going to find. I'll need to look.

[soul-soft]

Well, thank you very much.