MySQL Bugs: #89935: Entity framework is not working with the new connector version

Bug #89935	Entity framework is not working with the new connector version
Submitted:	6 Mar 2018 16:53	Modified:	7 Mar 2018 12:32
Reporter:	paulo paulo	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	Connector / NET	Severity:	S2 (Serious)
Version:	6.10.6	OS:	Windows (10)
Assigned to:		CPU Architecture:	Any
Tags:	connector, edmx, entity framework, NET

Description:
I installed first the mysql for visual studio 1.2.7, I have VS2015, VS2012 and VS2017 RC. (None of them are community versions) If I open visual studio 2015 (The one I am currently working) and go to Tools->Connect to Database I am able to see Mysql on the list.

And then I installed Mysql Connector 7.0.5, create a simple project (Web forms), then added a ADO NET Entity Data Model, specified Generate From Database and then when clicking on the new connection button I am not able to see Mysql.

I tried with another web project that already have a EDMX associated with mysql, also it does not open the edmx, it says:

Cannot load "testbd.edmx": Mysql.data.mysqlclient.mysqlProviderServices, MysqlDataEntity, Version=6.10.6.0, Culture=Neutral, PublicKeyToken=c5687fc88969c44d

I have added the binaries from C:\Program Files (x86)\MySQL\MySQL Connector Net 6.10.6\Assemblies\v4.5.2  to the bin folder of my Web Project and also added they as reference to the project.

How to repeat:
Install Vs2015
Install Mysql For Visual Studio 1.2.7
Install Mysql Connector 7.0.5
Open VS2015
Create a WebForms Application
Add a ADO Net Entity Data Model as "Ef Designer from database"
Click on New Connection 
There is no mysql on the list

On the description I talked about version 7.0.5 of the connector, in fact it is 6.10.6

unable to see mysql provider on the list

Attachment: mysqlproblem.PNG (image/png, text), 22.15 KiB.

Exception when opening existing edmx

Attachment: mysqlproblem2.PNG (image/png, text), 6.29 KiB.

Hello paulo,

Thank you for the bug report.
This is most likely duplicate of Bug #85908, please see Bug #85908

Thanks,
Chiranjeevi.

I checked the other bug you said, is there any workaround for working with EF on VS2015?