Could not load file or assembly system linq dynamic

Net, inspired by WireMock from the Java landscape. Dynamic Linq extensions for Microsoft. EntityFrameworkCore which adds Async support. Showing the top 5 popular GitHub repositories that depend on System. Skip To Content. Toggle navigation. Core 1. Package Manager. Core -Version 1. Core --version 1. The Example. UnitTest project calls the method flawlessly.

However, the Example. Mvc project, which references the same Example. Data project, throws the following exception:. Retrieve the LoaderExceptions property for more information. The system cannot find the file specified. I made the error go away by referencing the old DLLs of Castle. DynamicProxy2, Castle. Core, and log4net. I found them on RubyGems. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Accept Solution Reject Solution. Member 6-Mar am.

It was installed via NuGet, but for some reason it ignores System. Did you do a nuget on that separately to fix it? Kenneth Haugland 6-Mar am. There are several Reactive packages, did you install all of them? Linq, then it was throwing error that. Core is missing. With both of them everything works fine. BTW, I've found that Nuget does indeed miss dependencies sometimes. I'm sure it depends on how the package was built.

Add your solution here. OK Paste as. Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community. Already on GitHub? Sign in to your account. Is this backwards compatible with System. Library by Nathan Arnott? That lib seems to have disappeared and I am looking for a way to migrate my code.

I think I see you started with a fork from there. The text was updated successfully, but these errors were encountered:. Sorry, something went wrong. I pulled it using nugit and the only thing I had to do was change the using to have the correct namespace and it builds perfectly. I get the error below when I run the app immediately after building:. The odd thing is, if I run the app again without building it , it works without an error. The error occurs the first time I make a call to the dynamic linq api.

This is the stacktrace:.