twilio
Consider signing your nuget packages
Perhaps you should consider nuget signing:
https://docs.microsoft.com/en-us/nuget/create-packages/sign-a-package https://docs.microsoft.com/en-us/nuget/reference/signed-packages-reference
You'll get a blue checkmark in NuGet so people know it's the right package author (instead of knock-offs).
Hello @brockallen,
Thanks for reporting this!
This issue has been added to our internal backlog to be prioritized. Pull requests and +1s on the issue summary will help it move up the backlog.
With best regards,
Elmer
Somewhat related. You should give the assembly a strong name by signing it. As it is now, it cannot be used in a project that has a strong name. This is pretty unusual. I haven't seen a library that wasn't signed in a while.
I second the request to at least have the assembly Strong named. Anyone that chooses to use strong naming CANNOT use this library otherwise. We are having to make some difficult decisions as a result.
@sbansla still not done one year on. Can we expect this anytime soon?
@sbansla Any news on strong-naming the assembly itself? https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming
