> ## Content Index
> Fetch the complete content index at: https://blog.tsd.digital/llms.txt
> Use this file to discover other available public pages before exploring further.

# Could not load file or assembly xxx or one of its dependencies
- URL: https://blog.tsd.digital/could-not-load-file-or-assembly-xxx-or-one-of-its-dependencies/
- Published: 2020-05-11T07:51:27.000Z
- Updated: 2020-05-11T07:51:27.000Z
- Author: Tim Gaunt
- Tags: Development, Umbraco, #Import 2025-04-01 05:38

We hit the fairly common issue of not being able to resolve a dependency the other day and tried all the usual resolutions -checking that the version numbers across all projects match, check the values in the configs haven't corrupted during an install, clean and rebuild the solution, updated/reinstalled the nuget packages and nothing worked, we just kept hitting \`\`\` Could not load file or assembly 'Autofac, Version=3.5.0.0, Culture=neutral, PublicKeyToken=17863af14b0044da' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) \`\`\` The fix was ridiculously simple, in short, one of the app.configs had some out of date dependencies in the redirects -in this instance pointing at a newer version of Autofac from a failed upgrade so the fix was simply to correct the mappings. I didn't know that the app.config would affect the compiled assembly but it must overwrite the referenced DLL as the referenced versions were correct So in summary, the references were changed from: \`\`\` \`\`\` To this: \`\`\` \`\`\`