ASP.NET exception error mentions old version of MySQL.Data that is not used in app

This exception is not showing when debugging locally and shows up only when i browse to the remote url address of the server..

I have FTP'd the MVC 3 app to my remote server and a check of the Bin folder there shows that I have all three MySQL reference assemblies. All are version 6.4.4.0.

In my web.config file all of the version numbers relating to those are set to version 6.4.4.0.

Why am I getting this error message about version 6.3.6.0, and how can this be solved?

Could not load file or assembly 'MySql.Data, Version=6.3.6.0,culture=neutral, PublicKeyToken=c5687fc88969c44d' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Exception Details: System.IO.FileLoadException: Could not load file or assembly 'MySql.Data, Version=6.3.6.0, Culture=neutral, PublicKeyToken=c5687fc889开发者_运维知识库69c44d' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

---

There are a lot of things to check with this, but the most common one I've run accross was resolved by making sure the assembly is referenced correctly in the Visual Studio project and that the information is correct in the web.config.

In Visual Studio, check the properties on the references for the assemblies

• verify the the version listed.
• check if Specific Version is true/false.
• check if Copy Local is true.
• If the version is wrong, you may have to remove and re-add the reference.

I would guess the exception was not thrown on your local machine because the older version of the assemblies are available on your machine.

The reason your local information is showing in the exception is unrelated to the assembly reference issue. Your local system is where the assembly was built, and so that information is built in for debugging purposes. (If this exception was thrown while you were debugging, VS would bring you to that line of that file.)

---

Ok I was worried that I somewhere along the way bits of 6.3.6.0 where left on my system from when I had it installed.. After days of trying to figure this one out I actually have come up with the fix for this issue... I just simply needed to overwrite the version information using assembly binding in the web.config. Once I did that it loads from the remote server error free... Here is what I added to my web.config:

    <dependentAssembly>
    <assemblyIdentity name="MySql.Data" publicKeyToken="c5687fc88969c44d" />
    <bindingRedirect oldVersion="0.0.0.0-6.3.6.0" newVersion="6.4.4.0" />
    </dependentAssembly>

---

Could you please explain where I put the "Copy local = true" I do not see it as being part of any property window. I did find "Always Copy" for the resources. also where does this go in the web.config

<dependentAssembly> 
<assemblyIdentity name="MySql.Data" publicKeyToken="c5687fc88969c44d" /> 
<bindingRedirect oldVersion="0.0.0.0-6.3.6.0" newVersion="6.4.4.0" /> 
</dependentAssembly> 

---

I ran the package manager console and then used this to fix this problem:

PM> Install-Package MySQL.Data.Entities