Please add strong names to Hangfire assemblies

I’m in the general consensus that the HangFire assemblies should be signed

I agree it’s something that we can all do ourselves. However rather than push back asking why we all want it (plenty of valid reasons mentioned above), maybe you should tell us why you are resisting doing it? The fact that MS will or may not support it in the future will not wash. There is plenty of legacy code out there in production that needs this resolving.

I’m in the same boat, we have a policy that must be enforced which means we have to manually sign them each time we upgrade and of course, this negates the ease of using nuget for deployment. We are also a Pro subscriber and use the product in production

3 Likes