New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Missing Dapper.Contrib.StrongName #889

arthur-lopez opened this Issue Nov 28, 2017 · 1 comment


None yet
2 participants

arthur-lopez commented Nov 28, 2017


I would like to use dapper and dapper.contrib with strongName but i have only strongname for dapper. how can i create pull request for this one (easy feature)


This comment has been minimized.


NickCraver commented May 20, 2018

Update: what I'm planning on here is: a Dapper v2 release. The libraries will be strong named. There will be no other changes in v2. This is simply because strong naming is a breaking change. v3 will have the changes proposed in #722 and elsewhere (e.g. type mappers always running).

This will mean there will never be a Dapper.Contrib.StrongName, but Dapper.Contrib will start doing what you need.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment