Home/ Questions/Q 7819353
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-02T06:54:59+00:00

Setup: I have an app that is a copy of another app, that worked

  • 0

Setup:

I have an app that is a copy of another app, that worked with EF 4.1. In the new app, I have added a nuget package reference to EF 4.3.1 in a domain project.

All works on my local machine, but on the server throws the following error:

Could not load file or assembly 'EntityFramework, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Clearly, something is still referencing the old entity framework 4.1, but the only dll it finds is the EF 4.3.1 dll.

There are no references to EntityFramework in the web.config.

Question:

How do I find what is still referencing the old dll?

I have removed all EF references from all projects in the solution and added the EF 4.3.1 package to each project, but still no joy.

Notes:

I could try a binding redirect using the dependentAssembly (see accepted answer in this SO question)

However, I can’t find what names and tokens to use.

Still, it would be better to get to the route of the problem, rather than just redirecting a binding.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Have you recompiled the application after changing the reference, or just uploaded the new EntityFramework.dll file? It’s possible the application’s library is still referencing the old version in your production environment. Do a re-compile and re-publish.

    EDIT (see comments) : Open all your .csproj files in notepad and look for the Reference tags, double check that the old version doesn’t exist in all the projects.

    • 0