Home
Help
Register
Log in

Search

 
   Active Threads  

You are here: Home > LLBLGen Pro > Designer> LLBLGen 5.4.4 requiring old Devart?
 

Pages: 1
Designer
LLBLGen 5.4.4 requiring old Devart?
Page:1/1 

  Print all messages in this thread  
Poster Message
njbelf
User



Location:
Iowa City, Iowa, USA
Joined on:
07-Jun-2017 16:21:33
Posted:
70 posts
# Posted on: 23-Oct-2018 00:37:22.  
Hi,
Not sure what's going on here, but when I try to sync with a mysql database I get the following error:

Exception message:
-------------------------------
Exception type: FileLoadException
Could not load file or assembly 'Devart.Data.MySql, Version=8.10.1031.0, Culture=neutral, PublicKeyToken=09af7300eec23701' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Latest version of Devart.Data.MySql is 8.12.1229.0 which is what we are running. I tried putting binding redirects on all the config files I could find in the LLBLGen Pro V5.4 directory to no avail.
  Top
Otis
LLBLGen Pro Team



Location:
The Hague, The Netherlands
Joined on:
17-Aug-2003 18:00:36
Posted:
37186 posts
# Posted on: 23-Oct-2018 09:51:25.  
The designer isn't using a direct reference, it loads the assembly through the DbProviderFactory system in .NET. This system reads from the machine.config file the factory associated with the name "Devart.Data.MySql".

There are a couple of machine.config files on a system, one for 32bit and one for 64bit. Unless you explicitly start the 32bit runner, you start the designer in 64bit and therefore have to look in the machine.config file: c:\windows\Microsoft.NET\Framework64\config\machine.config

It should have a line like:
Code:
     <add name="dotConnect for MySQL" invariant="Devart.Data.MySql"
        description="Devart dotConnect for MySQL" type="Devart.Data.MySql.MySqlProviderFactory, Devart.Data.MySql, Version=8.12.1229.0, Culture=neutral, PublicKeyToken=09af7300eec23701" />


So either you're running the designer by accident as 32bit (and therefore use an outdated machine.config file) or the machine.config file isn't updated by the installer of devart.

But in any case: our code doesn't have any reference with an ado.net provider other than sqlclient: they're all loaded through DbProviderFactory.


Frans Bouma
LLBLGen Pro / ORM Profiler Lead Developer | Blog | Twitter
 
Top
njbelf
User



Location:
Iowa City, Iowa, USA
Joined on:
07-Jun-2017 16:21:33
Posted:
70 posts
# Posted on: 23-Oct-2018 16:30:46.  
Otis wrote:
The designer isn't using a direct reference, it loads the assembly through the DbProviderFactory system in .NET. This system reads from the machine.config file the factory associated with the name "Devart.Data.MySql".

There are a couple of machine.config files on a system, one for 32bit and one for 64bit. Unless you explicitly start the 32bit runner, you start the designer in 64bit and therefore have to look in the machine.config file: c:\windows\Microsoft.NET\Framework64\config\machine.config

It should have a line like:
Code:
     <add name="dotConnect for MySQL" invariant="Devart.Data.MySql"
        description="Devart dotConnect for MySQL" type="Devart.Data.MySql.MySqlProviderFactory, Devart.Data.MySql, Version=8.12.1229.0, Culture=neutral, PublicKeyToken=09af7300eec23701" />


So either you're running the designer by accident as 32bit (and therefore use an outdated machine.config file) or the machine.config file isn't updated by the installer of devart.

But in any case: our code doesn't have any reference with an ado.net provider other than sqlclient: they're all loaded through DbProviderFactory.


Thank you for that bit of information. We did indeed have an old DBProvider in our machine.config.
  Top
Pages: 1  


Powered by HnD ©2002-2007 Solutions Design
HnD uses LLBLGen Pro

Version: 2.1.12172008 Final.