Dapper SetTypeMap Breaks ClassMapper

[danielearrighi]

Hello, In my project I'm using a custom SqlMapper to map my Db columns in dapper, but when I setup Dapper to user my custom type mapper by doing: Dapper.SqlMapper.SetTypeMap(typeof(User), new UserMapper()); Suddently, DapperExtension is no more able to Map my User class so that when I do: User item = cn.Get<User>(id); The item contains only default values.

My UserMapper does not interfere with ClassMapper implementation from DapperExtensions.

Any suggestion? Thank you for your help

[danielearrighi]

After a further investigation, I've finally found and solved the problem: Say I have a TestClass with property Id mapped in my UserMapper to the database column UserId.

• When Dapper executes the query (ex. SELECT * FROM Users), it ask to my UserMapper to which property it can map the column "UserId" (=> Id).
• When DapperExtension executes the query, it ask to my UserMapper to which property it can map the column "Id" (=> ?). This because DapperExtension executes the query like "SELECT UserId As Id FROM Users" so the column is already mapped, but my UserMapper cannot find an IPropertyMap mapped with Name = Id.

Solved by checking if the search for a IPropertyMap with ColumnName = Id fails; if so, I fallback by searching for an IPropertyMap with Name = Id.

If you think this can be solved in a better way, please let me know Thanks!

[valfrid-ly]

Could you design an unit test for this particular case so I can put it to be validated ?

Thanks