All geek questions in one place

Adding a strong name / signature to an external DLL?

We sign our library, but one of our external dependencies itself is not signed, which gives us the following error:

Referenced assembly 'ManyConsole' does not have a strong name

We get the ManyConsole package (excellent BTW!) Via Nuget, but in the order of an orphan not affiliated with Nuget, which we signed. In fact, we could very well sign it with the same key as our own application, but it is not clear how we can sign the “external” DLL.

+6
source share
3 answers

I had the same problem with a third-party NuGet package that was not signed, but my project required all assemblies to be signed.

I installed the NuGet StrongNameSigner package, which automatically signs all unauthorized assemblies. It did a great job. Easy to install, just install the package, no need to configure anything. Works out of the box.

+1
source

Maybe this post, especially the answer from x0n, will help. It helps me.

Strong third-party assembly naming - Failed to load file or assembly

0
source

Source: https://habr.com/ru/post/954215/

More articles:


All Articles