Licensing broken

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
FransBouma
Posts: 29
Joined: Fri 25 Nov 2005 10:43

Licensing broken

Post by FransBouma » Sat 28 Jan 2006 23:42

.EXE has this line in licenses.licx file:
CoreLab.MySql.MySqlConnection, CoreLab.MySql, Version=3.20.7.0, Culture=neutral, PublicKeyToken=09af7300eec23701

.EXE uses dynamically loaded assembly which references corelab's MySql provider 3.20.7.
All works fine.

CoreLab's provider is updated to 3.20.8.0

-> Exe gives dreaded license not found error.

If line in .exe's licenses.licx file is updated to:
CoreLab.MySql.MySqlConnection, CoreLab.MySql, Version=3.20.8.0, Culture=neutral, PublicKeyToken=09af7300eec23701

and recompiled, .exe works again.

But... .exe is a program used by 3rd parties which buy the mysql provider themselves. So if they upgrade, the .exe stops functioning.

It gets worse:
The .exe with CoreLab.MySql.MySqlConnection, CoreLab.MySql, Version=3.20.8.0, Culture=neutral, PublicKeyToken=09af7300eec23701 in the licenses.licx file can't be used with the mysql provider v3.20.7. It won't work, license error.

I've no idea why on earth it gives this error because I have a valid license for v3 std and frankly I'm a little tired of all these errors. We can't give out a new .exe every week just because you released a new version and ask all our customers who use mysql to upgrade to your newest version if they want to use the new .exe because it would otherwise not work with their CURRENT installed version.

Please a.s.a.p. update your check code so that it checks for 3.x.y.z instead of the same 3.x version of the dll the code is in.

Paul
Posts: 725
Joined: Thu 28 Oct 2004 14:06

Post by Paul » Wed 01 Feb 2006 10:13

We fixed this problem. This fix will be included in the next MySQLDirect
.NET build in a few days.
You can compile your application with any version of MySQLDirect .NET but it
will work with this version and other builds starting from the next one.

cjendro
Posts: 18
Joined: Sun 25 Dec 2005 14:35
Contact:

Post by cjendro » Sun 05 Feb 2006 19:43

Paul wrote:We fixed this problem. This fix will be included in the next MySQLDirect
.NET build in a few days.
You can compile your application with any version of MySQLDirect .NET but it
will work with this version and other builds starting from the next one.


*hope*

Post Reply