Dapper.Contrib strong name nuget package

[maggarwal]

Hi,

There is no strongly named nuget package for Dapper.Contrib. Right now only solution is to actually copy the code from repo into my own code, which is hard to maintain.

[NickCraver]

We'll make sure Dapper and Dapper.Contrib are both strong named (without different packages for this) in v2. For now, you can use https://www.nuget.org/packages/Brutal.Dev.StrongNameSigner/ to do this during a build.

[damiangonzalez]

Nick,
Thanks for the info. For now I've decided to compile the code into ours, but we will adjust as soon as signed assemblies are available from your team.

[mgravell]

We should just get this done. Very tempting to say "April 1st" simply for the jollies, but no real reason we can't do sooner.

…

On 27 Jan 2017 9:46 p.m., "damiangonzalez" ***@***.***> wrote: Nick, Thanks for the info. For now I've decided to compile the code into ours, but we will adjust as soon as signed assemblies are available from your team. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#685 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABDsNdcofJaPtSLI18AdgSnYlHsVxZ8ks5rWmXFgaJpZM4LtHSG> .

[NickCraver]

See #889 for an update here - collapsing so we're on the same issue.