.NET Standard Packages Not Signed?

[Nick S]

Hello! I'm working on converting a web site that uses RavenDB to .NET Core, and all of the assemblies for the site are signed. I've added the RavenDB client dependency to one of my supporting projects which targets .NETStandard 1.4. The project fails to build, complaining that the RavenDB assemblies are not signed. Upon investigation, it seems that the 3.5.3 libraries pulled from NuGet that target .NETStandard1.3 are indeed unsigned. The ones targeting the full .NET 4.5 are signed properly. Is this a known issue?

Thanks!

Nick S

[Grzegorz Lachowski]

Hi Nick,

Strong-naming is not recommended anymore, so we stopped signing our net_standard assemblies. Please have a look here:

https://github.com/dotnet/corefx/blob/master/Documentation/project-docs/strong-name-signing.md#1-microsoft-strong-names-their-assemblies-should-i

https://www.pedrolamas.com/2016/03/01/still-strong-naming-your-assemblies-you-do-know-its-2016-right/

If you want to use Raven.Client with your strong-named library you can sign Raven.Client dlls like so:

https://stackoverflow.com/questions/331520/how-to-fix-referenced-assembly-does-not-have-a-strong-name-error/30150904#30150904

[Nick S]

Ah, I see. Thanks for the info. Out of curiosity, why are you then still signing the libraries targeting the full framework? For backward compatibility?

I'm not exactly sure how this multi-targeting is supposed to work, but it does seem that I'm unable to have a .NET Standard library (which contains my indexes) reference RavenDB 3.5.3, and then have my legacy MVC site (targeting the full .NET framework) reference that library (to access the index definitions). The build errors out because the legacy MVC project does not reference the library that defines the base classes for my indexes, even though it does have a reference to RavenDB 3.5.3 (just with a different target). Is this possibly because one is signed and one is not?

Interestingly, I have no such issue with another project (which contains my entity definitions), even though it targets .NET Standard 1.4 and references Newtonsoft.Json.

Thanks,

Nick

[Grzegorz Lachowski]

Yes, for backward compatibility.

I haven't tried that myself yet, but consider your build directory. Which of Raven.Client dlls is going to land in that directory, since you reference both of them?