Home/ Questions/Q 3597072
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T20:04:16+00:00

I’m having another of these "Could not load file or assembly or one of

  • 0

I’m having another of these "Could not load file or assembly or one of its dependencies" problems.

Additional information: Could not load
file or assembly
‘Microsoft.Practices.Unity,
Version=1.2.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35’ or
one of its dependencies. The located
assembly’s manifest definition does
not match the assembly reference.
(Exception from HRESULT: 0x80131040)

I have no idea what is causing this or how I could debug it to find the cause.

I’ve done a search in my solution catalogs .csproj files, and every where I have Unity I have:

Reference
Include="Microsoft.Practices.Unity,
Version=2.0.414.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35,
processorArchitecture=MSIL"

Can’t find any reference anywhere which goes against 1.2.0.0 in any of my projects.

Any ideas how I should go about solving this?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    1. Check if you are referencing an assembly which in turn referencing an old version of unity. For example let’s say you have an assembly called ServiceLocator.dll which needs an old version of Unity assembly, now when you reference the ServiceLocator you should provide it with the old version of Unity, and that makes the problem.

    2. May be the output folder where all projects build their assemblies, has an old version of unity.

    You can use FusLogVw to find out who is loading the old assemblies, just define a path for the log, and run your solution, then check (in FusLogvw) the first line where the Unity assembly is loaded, double click it and see the calling assembly, and here you go.

    • 0