Skip to content

Could not load file or assembly 'dotNetRdf.Client' or one of its dependencies. Strong name signature could not be verified. #591

Closed Answered by kal
berezovskyi asked this question in Q&A
Discussion options

You must be logged in to vote

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:

  • You will not be able to install the assembly to the Global Assembly Cache (GAC)
  • You will not be able to load the assembly in an AppDomain where shadow copying is turned on.
  • You will not be able to load the assembly in a partially trusted AppDomain
  • You will not be able to pre-compile ASP.NET applications

I'm guessing that it is that last bullet that is the problem for you? Do you precompile the ASP.NET applic…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@berezovskyi
Comment options

Answer selected by berezovskyi
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants