search

JasperFx / lamar

Fast Inversion of Control Tool and Successor to StructureMap
https://jasperfx.github.io/lamar
MIT License
568 stars 119 forks source link

Strong name signing for the assembly #194

Closed stefandascalu64 closed 4 years ago

stefandascalu64 commented 4 years ago

I am using Lamar in a project that has a strong name key and the fact that this binary is not signed is causing some problems when I try to publish. Are there any plans to add this in the future so I can use nuget.org binaries instead of my current annoying workaround?

jeremydmiller commented 4 years ago

Lamar is very purposely not signed and will not likely be in the future.

Have you tried StrongNamer as a workaround?

stefandascalu64 commented 4 years ago

yes, but after some issues we ended up giving up on the whole mess. Can you tell me the reason why it is "very purposely not signed"

jeremydmiller commented 4 years ago

Strong naming causes a whole lot of pain downstream, especially for libs like Lamar that will be diamond dependencies. This isn't a new discussion by any stretch of the imagination.