Adding a strong name / signature to an outside DLL?
We're signing our library but one of our external dependencies is itself
not signed, giving us the following error:
Referenced assembly 'ManyConsole' does not have a strong name
We get the ManyConsole package (a great one BTW!) via Nuget but are ok
with a non-Nuget orphan that is signed by us. In fact, we could very well
sign it with the same key as our own app but it's not clear how we can
sign an "outside" DLL.
No comments:
Post a Comment