Please add strong names to Hangfire assemblies

[phaedrus30]

I’ve already posted why we need it in this thread.

Why we need Hangfire to be strongly named

I’ve posted on this before but I want to re-iterate why it is important to us, and I would really like to know when it will become available. We are required for compliance reasons to strong name all our application assemblies - because Hangfire is not strongly named, we simply cannot use the default NuGet distribution. In order to use Hangfire, I had to do the following: Use the Nivot package from NuGet to apply a strong name to unsigned assemblies (Dapper, HangFire.Core, HangFire.SqlServe…

I don’t care what vNext is doing - we need this support now. If things change in the future, then so be it.

Plus, I’ve already strong named Hangfire myself, it took me 5 minutes, so I don’t know what could possibly be the issue for you to do it from your side.