CoreLab.MySql.Entity issue

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for MySQL
Post Reply
AG
Posts: 13
Joined: Tue 11 Mar 2008 11:26

CoreLab.MySql.Entity issue

Post by AG » Sun 29 Jun 2008 18:09

Hello

I have to say (with regret) that every MyDirect build makes it worse and worse.
After migration to 4.70.30.0 it's absolutely impossible to edit any typed dataset with dataset designer. Dataset designer does not recognize connection strings from project settings. When I create new connection its providerName is always CoreLab.MySql.Entity and there is no way to change it. I have tried to remove CoreLab.MySql.Entity from machine.config and from GAC - no effect.
To reproduce open your crm_demo project, open CrmDemoDataSet.xsd with dataset designer and try to change any select statement in any table.

Now it seems like I have to rollback to 4.50 with its terrible bugs because bugs in 4.70 are much more terrible for me.

anton.connect
Posts: 43
Joined: Thu 19 Jun 2008 14:30

Post by anton.connect » Tue 01 Jul 2008 08:00

Thank you for the bug report.
We have reproduced the problems and now we are trying to solve them.
We let you know on the result.

anton.connect
Posts: 43
Joined: Thu 19 Jun 2008 14:30

Post by anton.connect » Tue 01 Jul 2008 12:56

We have fixed this problem. This fix will be included in the next build of MyDirect .NET

Regards,
Anton

Post Reply