Search code examples
c#dllstrong-named-key

What would happen if signed DLL replaced with un-signed?


We have a bunch of libraries that are strong-named and placed in the GAC. We are trying to get away from the practice. Here is the scenario I need to address at the moment.

I have a DLL (to replace and existing and signed one, same name and overall structure) which I cannot sign or strong name properly, as we cannot reproduce the key. I will recompile a component/code using the unsigned version and later deploy it with unsigned copy, using . If remove the signed copy from GAC, will the other components (who would use the same probing) consume the new one without recompile or still demand the signed version?

Thank you.


Solution

  • strong-name signatures are not validated when an assembly is loaded into a full-trust application domain. more information about this bypass feature can be found in this link.Hope it helps