# Please add strong names to Hangfire assemblies

**URL:** <https://discuss.hangfire.io/t/please-add-strong-names-to-hangfire-assemblies/339>\
**Category:** feature\
**Created:** [October 30, 2014, 5:10am UTC](https://discuss.hangfire.io/t/please-add-strong-names-to-hangfire-assemblies/339 "2014-10-30T05:10:21Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![phaedrus30](https://avatars.discourse-cdn.com/v4/letter/p/898d66/32.png) [@phaedrus30](https://discuss.hangfire.io/u/phaedrus30)\
**Post date:** [December 8, 2014, 9:45pm UTC](https://discuss.hangfire.io/t/please-add-strong-names-to-hangfire-assemblies/339/6 "2014-12-08T21:45:59Z")

</div>

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

> [@Why we need Hangfire to be strongly named](http://discuss.hangfire.io/t/why-we-need-hangfire-to-be-strongly-named/405):
>
> 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.

---

_[View the full topic](https://discuss.hangfire.io/t/please-add-strong-names-to-hangfire-assemblies/339)._