Why won't AutoMapper v3 work because it's looking for v2.2.1.0?

Question

I just installed AutoMapper, via nuGet, on a new project, but when I run the code, I get the following error:

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

Why is it looking for Version=2.2.1.0, and what can I do about it? Revert to that version?

score 12 · Accepted Answer · answered Sep 02 '13 at 13:42

12

You probably just want to add a binding redirect for AutoMapper as one of your references is looking for version 2.2 specifically

This should do it:

 <dependentAssembly>
      <assemblyIdentity name="AutoMapper" publicKeyToken="be96cd2c38ef1005" 
                     culture="neutral"/>
      <bindingRedirect oldVersion="0.0.0.0-3.0.0.0" newVersion="3.0.0.0"/>
    </dependentAssembly>

answered Sep 02 '13 at 13:42

dove

20,469
14
82
108

in fact I just updated to 3.0 and got the issue you had and fixed it by adding this binding redirect. if you have .net reflector you could probably see what has this reference but it is probably rather academic really. – dove Sep 02 '13 at 15:03

score 4 · Answer 2 · answered Sep 02 '13 at 11:16

4

Try uninstalling and reinstalling AutoMapper again.

If you have multiple projects in your solution chances are that you have version 2.2.1.0 already installed in one of your projects. But latest version of AutoMapper is 3.0.0 so this is why you got problems.

answered Sep 02 '13 at 11:16

TheNick

69
1
5

This is entirely possible. I will double check that as soon as I get to work on the code again tonight. – ProfK Sep 02 '13 at 14:33

score 1 · Answer 3 · answered Jan 26 '15 at 13:20

Problem:

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

Solution:

Add assemblyBinding to yur app.config files:

<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="AutoMapper" publicKeyToken="be96cd2c38ef1005" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-3.2.1.0" newVersion="3.3.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

Clean, Rebuild solution and smile! :-)

score 0 · Answer 4 · answered Feb 18 '14 at 01:52

0

I had the same error and was able to fix by setting Enable 32-Bit applications to True on the App Pool

answered Feb 18 '14 at 01:52

Aussie Ash

1,276
12
10

Why won't AutoMapper v3 work because it's looking for v2.2.1.0?

4 Answers4