Having used LLBLGen successfully for many years on MsSqlServer, I am currently working on a new project where we had to use an open source database. I needed to generate a data layer for Sqlite, but LLBLGen doesn't support this product (and doesn't plan to), so I decided to go with MySql (v5.1.31-community) and later export the data to the Sqlite file. I thought it would be trivial to get LLBLGen to generate the classes from MySql.

I have followed the guidelines in this forum for installing the CoreLab MySql driver, from here - http://devart.com/dotconnect/mysql/download.html - but I can't get past the 'Create new project' / 'Test Connection' dialog in LLBLGenPro v2.6.

The error is, of course: 'Could not load file or assembly 'CoreLab.MySql, Version=4.0.9.0, Culture=neutral, PublicKeyToken=09af7300eec23701' or one of its dependencies. The system cannot find the file specified.'

I have tried installing both the Enterprise and free versions of the Devart MySql driver (actually, it's Devart dotConnect for MySql - dcmysql.exe), but no luck. There is no 'Corelab.MySql' file anywhere on my machine, although I realise that the file may be called something else (?)

MySql is installed locally, and I can connect to it via the MySQL Administrator program. I don't know what else I have to do to get LLBLGen to connect.

Can you please give me a suggestion? Thanks.

Operating system is Windows XP, MySql version 5.1.31, LLBLGen version: 2.6 Demo.

Ok, I've managed to connect by downloading and installing the 'MyDirect .NET 4.85 Trial'. (http://download.devart.com/File.aspx?prod=dotconnect/mysql&file=mysqlnet.exe)

I didn't do this initially because of this note next to the download:

Note: This version is available for backward compatibility with .NET Framework 1.0 and 1.1

Is this the right version to use?

That version is ok. This is the problem with v5: http://llblgen.com/TinyForum/Messages.aspx?ThreadID=14728

It's becoming more and more a problem and we hoped DevArt would at least be gentle and supply CoreLab build providers as well, but no chance (only for .net 1.x)

The only thing we can do is back-port our work done on the v3 driver for mysql to v2.x and the DQE so that it uses the dbproviderfactory and not the fixed namespaces/typenames.

I'm not sure if this will be without other problems, e.g. users who use .NET 1.x versions of the MySqlDirect provider will not be able to use llblgen pro all of a sudden because the dbproviderfactory is a .net 2.0 class, but at the moment, users who start with mysql now are in trouble. We'll look into this.