Closed Angst003 closed 5 years ago
Sorry for the late response, I somehow missed this issue. As far as I can tell, Dapper it self isn't strongnamed. This is metadata from the latest Dapper version downloaded from nuget.org:
When PublicKeyToken=null, you can pretty much assert that the assembly isn't strongly named. And as long as Dapper itself don't have a strong name, we cannot strong name either.
Hi, I know Dapper is not strongly named but Dapper.StrongName is...
`<?xml version="1.0" encoding="utf-8"?>
Ah, my misunderstanding, sorry. That should be easy enough, just need to add another project file that generates a strong named assembly, and a new nuget package with the strong named assembly in it.
There is now a strong-named alternative: Dapper.Oracle.StrongName Exactly the same package, except it is strong-named, and depends upon Dapper.StrongName
Closing issue again.
Great thank you very much.
Hi,
Is it possible to have a signed assembly version of this library ? Dapper has a Dapper.StrongName.