Could not load file or assembly. A strongly-named assembly is required

▲
0
▼

When i call an endpoint on my web api project, i get this error -

Could not load file or assembly 'System.Linq.Dynamic, Version=1.0.5840.25917, Culture=neutral, PublicKeyToken=null' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

i cannot seem to sign this assembly- System.Linq.Dynamic.dll with a strong name using Visual Studio 2017 (see attached image).

if i use the command line it seems to work, however using visual studio 2015, it doesn't seem to sign the dll with a strong name.

enter image description here

enter image description here

c#
.net
visual-studio
.net-core
.net-assembly
asked on Stack Overflow Dec 13, 2017 by Kojof • edited Dec 16, 2017 by Lex Li

2 Answers

▲
4
▼

You can read System.Linq.Dynamic.Core to see how many forks of System.Linq.Dynamic are there.

The openness allows you to choose another NuGet package which ships a strong named assembly for the project, and that solves the issue.

Hope one of the forks would grow and one day becomes the "upstream" :)

answered on Stack Overflow Dec 15, 2017 by Lex Li
▲
0
▼

I had a similar (same) error (different cause):

Could not load file or assembly 'xx' or one of its dependencies. A strongly-named assembly is required. (Exception from HRESULT: 0x80131044)

It turned out that the Project ('xx') in my solution, that I referenced from another project was not set to build in Debug mode. When I selected Properties (F4) of the project ('xx') in Visual Studio, it turned out that the value for "Always Start When Debugging" was set to False.

I set it to True, and the error was resolved.

answered on Stack Overflow May 4, 2021 by Jonno

User contributions licensed under CC BY-SA 3.0