Unable to use this assembly because it is not strong name signed

[alex4998]

All our projects generate strong name signed assemblies and strong name signed assemblies cannot reference non-strong name signed ones.

CSC : warning CS8002: Referenced assembly 'MassiveDynamicProxyGenerator, Version=1.5.0.0, Culture=neutral, PublicKeyToken=null' does not have a strong name.

Would it be possible to update this project and add the strong name signing?

[harrison314]

Which runtime do you use on the project?

A strong name is not recommended for .Net Core projects. I'd probably have to do a new nuget package MassiveDynamicProxyGenerator.StringName nugget, just like https://www.nuget.org/packages/StackExchange.Redis.StrongName/.

[alex4998]

Hi, In our case the project is build for .NET Framework 4.6.2. Thank you, Alex From: Jozef Gajdoš ***@***.***> Sent: Wednesday, May 5, 2021 13:33 To: harrison314/MassiveDynamicProxyGenerator ***@***.***> Cc: alex4998 ***@***.***>; Author ***@***.***> Subject: Re: [harrison314/MassiveDynamicProxyGenerator] Unable to use this assembly because it is not strong name signed (#24) Which runtime do you use on the project? A strong name is not recommended for .Net Core projects. I'd probably have to do a new nuget package MassiveDynamicProxyGenerator.StringName nugget, just like https://www.nuget.org/packages/StackExchange.Redis.StrongName/. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#24 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/ADSR3MZX42UX4QCCEGHONJ3TMGFPPANCNFSM44FJKVMA> . <https://github.com/notifications/beacon/ADSR3M2Y2B6CCKYTPGO5AJLTMGFPPA5CNFSM44FJKVMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOGGSUUQQ.gif>

…

-- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

[harrison314]

I have some problems with Strongname signing in .Net 5 and .Net Core SDK.

StrongNamer nuget could solve your problem.

[wasabii]

The guidance that strong naming is not "recommended" is false:

Create strong named .NET libraries

You should strong name your open-source .NET libraries if their targets include .NET Framework or .NET Standard. Strong naming is not required for libraries that target .NET Core/5+ only.

Note

This guidance is specific to publicly distributed .NET libraries, such as .NET libraries published on NuGet.org. Strong naming is not required by most .NET applications and should not be done by default.

https://learn.microsoft.com/en-us/dotnet/standard/library-guidance/strong-naming

Basically, if you are publishing a public library, for distribution for Framework users, it is still recommended you strong name, for exactly the reason encountered by the user above.

[harrison314]

I added strong name assembly for .Net Framework DLL to MassiveDynamicProxyGenerator 1.7.1. Please check if this helped.