Could not load file or assembly 'dotNetRdf.Client' or one of its dependencies. Strong name signature could not be verified. #591
-
Hi, I am trying to update our OSLC4Net SDK from .NET 4.8 / dotNetRDF 1.0 to .NET Standard 2.0 + dotNetRDF 3.0.1 (.NET 6.0+ if .NET Standard 2.0 turns out to be insufficient). I ran into the following issue after doing the migration when trying to use our newly migrated libraries under ASP.NET MVC 5 and .NET 4.8 (we are in process of migrating those too):
I found #562 to be related, but not sure if the error is caused by a mistake on my side or the incomplete signing from the dotNetRDF side. Thank you in advance for the help! Stacktrace
P.S. I tried to remove the dependency on dotNetRDF and replace it with a dep only on Details
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Hi @berezovskyi With the 3.0.1 release we did change the assemblies to be "fake signed" using the PublicSign option. This appears to be the recommended approach for OSS libraries. However I have just found this document which lists the limitations of public signing as an approach:
I'm guessing that it is that last bullet that is the problem for you? Do you precompile the ASP.NET application? If you don't precompile, does the application load OK or do you still get an error? When I changed the signing to PublicSign I didn't know that there was that restriction and that does feel like its a real problem for migrating ASP.NET applications to the 3.0 release and maybe means that we should reinstate the full signing of the assemblies, but before doing that it would be good to know if this really is the problem you are hitting! |
Beta Was this translation helpful? Give feedback.
Hi @berezovskyi
With the 3.0.1 release we did change the assemblies to be "fake signed" using the PublicSign option. This appears to be the recommended approach for OSS libraries. However I have just found this document which lists the limitations of public signing as an approach:
I'm guessing that it is that last bullet that is the problem for you? Do you precompile the ASP.NET applic…