-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Strong Name #4
Comments
@ChrisMissal Thoughts on this? None of our packages are signed. I wouldn't want signed assemblies in most cases due to the problem of binding redirects when we push a new bug fix. We could offer a second package that is signed, but that means we have to maintain those two packages. I suppose another alternative would be to vary the assembly version and assembly file version to avoid the binding redirect issue. Here's a good post on the topic: http://codebetter.com/sebastienlambla/2011/01/05/strong-naming-assemblies-and-openwrap/ |
I'm going to maintain a strong stance of "no" on this one. A few reasons:
Just my thoughts, I'm not trying to be a jerk about it, I just have a strong opinion. |
Somewhat related: I've been wondering if we should offer |
While I agree with all the arguments against, I will only make one argument for signing - this DLL has a dependency on StructureMap DLL, which is actually signed. |
That may not be relevant as StructureMap 3 is no longer signed and Jeremy Miller has made it clear that he has little interest in doing so. |
It would be nice to give assembly included in WebApiContrib.IoC.StructureMap package a strong name, just in case someone has a policy to sign all assemblies.
Thank you.
The text was updated successfully, but these errors were encountered: