Strong naming

[repko-artem]

Thanks lot for the library!
Do you have any plans to sign your library? It's not possible now to use your NuGet package in solutions that require strong naming.

[tihomir-kit]

Yeah, it has been on my mind for some time, I should do it. I'll do it for the next release.

[GeorgeHahn]

If you do this, please retain a non-strong named version on Nuget. It looks like many projects append .StrongName to their strong named binaries. This is desirable for a number of reasons that I won't go into here - but there's lots of discussion around the web:

reactiveui/ReactiveUI#43
libgit2/libgit2sharp#212
ericsink/SQLitePCL.raw#53
octokit/octokit.net#405
twilio/twilio-csharp#298 (comment)

[tihomir-kit]

Great, info, didn't know that. I'll check it out, thanks.

[mdy6]

Hi,
I want to use your library, but i have the same Strong naming issue.
Have you already figure out this ?
Thanks

[GillesTourreau]

Hi @pootzko,

We have the same issue here...
All our projects are signed with strong name and we can not use directly the library...
We need to get all the source code of InfuxData.Net project and compile with a strong name in our side... :-(

Hope that you will be able to fix this issue soon...

[dprothero]

There are various options you can take to deal with this issue:

https://support.twilio.com/hc/en-us/articles/360008375953-Does-Twilio-provide-a-strong-named-assembly-of-the-C-helper-library-