Bug #58181 Assembly Manifest Error
Submitted: 14 Nov 2010 13:14 Modified: 16 Nov 2010 15:41
Reporter: Bill Martschenko Email Updates:
Status: Closed Impact on me:
Category:Connector / NET Severity:S1 (Critical)
Version:6.3.5 OS:Windows (7)
Assigned to: Reggie Burnett CPU Architecture:Any

[14 Nov 2010 13:14] Bill Martschenko
In the v2.0 install folder of the 6.3.5 download for the .NET connector:

MySql.Data.Entity.dll is version 6.3.4 and makes a strong assembly ref to 6.3.4 MySql.Data.dll.

MySql.Data.dll is version 6.3.5 in the package.

Looks like it is a simple build issue.  I downloaded the source to see whether a project reference was used rather than a file reference.  That build was broken.

How to repeat:
Just download and install the msi and look at the v2.0 folder with ILDASM or .NET Reflector to check the assembly manifest of MySQL.Data.Entity.dll.

The assembly manifest for the entity dll shows the wrong version.  

A simple query run against gives this exception:

Schema specified is not valid. Errors: 
VTigerModel.Model1.ssdl(2,89) : error 0004: Could not load file or assembly 'MySql.Data.Entity, Version=, 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)

Suggested fix:
Build MySQL.Data.Entity.dll 6.3.5 for the MSI.
[15 Nov 2010 7:04] Tonci Grgin
Bill, verified just as described on Win7x64 Ultimate using 6.3.5 msi, full install.
[16 Nov 2010 15:41] Reggie Burnett
This bug is verified and does exist however it's not a *bug* in the normal sense of the word.  I have confirmed the problem but since there is no code to change I'm closing this bug and making a note that we need to make a 6.3.6 release *soon* to fix this issue.