The located assembly's manifest definition does not match the assembly reference

cwest · Post by **cwest** » Sat 01 Dec 2007 22:47

I just purchased v 4.25.22.0 of mysql direct. Now when I try to deploy my project, I've getting the error:

Could not load file or assembly 'CoreLab.MySql, Version 4.0.9.0 ...
The located manifest definition dows not match the assembly reference.

What's odd is that I check the dll version in the deployed app and it's 4.25.22.0. There are no corelab assemblies in the GAC.

My Previous builds were using the 30 day trial. I've uninstalled the trial version, and in my project I reference the dlls provided with the new full corelabs installation. What am I doing wrong?

Serious · Post by **Serious** » Mon 03 Dec 2007 12:57

Check your application config file and also make sure that there are no policy files in the GAC.

cwest · Post by **cwest** » Mon 10 Dec 2007 14:19

I uninstalled all of the policy files for corelbs in the GAC. My app.config contains only a connection string.

I just tried re-building after removing the poilicy files and deleting the bin directrories entirely. I'm still getting the same thing. My build output shows the following:

Consider app.config remapping of assembly "CoreLab.MySql, Culture=neutral, PublicKeyToken=09af7300eec23701" from Version "4.0.9.0" [] to Version " 4.25.22.0" [C:\data\VSProjects\cm\DAL\bin\Release\CoreLab.MySql.dll] to solve conflict and get rid of warning.
C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Microsoft.Common.targets : warning MSB3247: Found conflicts between different versions of the same dependent assembly.

I don't know how to do the re-mapping, but why should I have to? I've completely un-installed the trial version and searched my entire computer for any references to 4.0.9.0 . I have no idea where this is coming from. I've deleted and re-added the references to the corelabs dlls and triple checked the versions numbers on them too.

What's next?

Serious · Post by **Serious** » Tue 11 Dec 2007 12:59

Looks like dependent assemblies in your project reference different versions of MyDirect .NET. Check if your application references the same CoreLab.MySql assembly version as LLBLv.

cwest · Post by **cwest** » Tue 11 Dec 2007 15:25

The code generated by LLBL is using Corelab.Mysql v.4.25.22.0 & Corelab.data v.4.25.18.0 - the same as my application references.

Ideas?

Serious · Post by **Serious** » Tue 11 Dec 2007 16:32

Check if this blog post will help you.

Serious · Post by **Serious** » Thu 13 Dec 2007 09:47

It is possible to re-bind assemblies with following lines in the App.settings file:

Code: Select all

Add following lines to your App.config file:



...
 
  
   
    
    
   
  
 
...

Devart Forums

The located assembly's manifest definition does not match the assembly reference

The located assembly's manifest definition does not match the assembly reference

Which llbl references are you refering to?