Bug #88507 Adding "ADO.NET Entity Data Model" as "EF Designer from database" does not work
Submitted: 15 Nov 2017 22:16 Modified: 31 Mar 2018 16:32
Reporter: Matt Bilek Email Updates:
Status: Verified Impact on me:
None 
Category:MySQL Visual Studio Integration Severity:S1 (Critical)
Version:1.2.7 OS:Microsoft Windows (Microsoft Windows 10)
Assigned to: CPU Architecture:Any
Tags: ADO.NET Entity Data Model, EF Designer from database, Entity Framework 6.x, mysql for visual studio, MySQL Visual Studio Integration

[15 Nov 2017 22:16] Matt Bilek
Description:
When attempting to add an "ADO.NET Entity Data Model" as "EF Designer from database" using a successfully tested connection, once the "Finish" button is clicked the dialog box disappears and the Model was not created nor the Web.Config file was updated.  It does not matter if the radio button is set to "No" or "Yes" for sensitive data in the connection string.  Also, the Model is still not generated when the Web.Config checkbox is unchecked.  I have attempted countless permutations/combinations of the following versions with no avail.

Requirements:
MySQL Server 5.7 or greater
Microsoft Entity Framework 6.x
Microsoft Visual Studio 2017

NOTE: Please do not not give me other versions to try.  I have already attempted multiple combinations of versions.  Need an actual combination that has be tested and proven.  I have also tried just about every workaround that has been posted on the internet with luck.

Or is this a bug?

How to repeat:
Add an "ADO.NET Entity Data Model" as "EF Designer from database" using a successfully tested connection, once the "Finish" button is clicked the dialog box disappears and the Model was not created nor the Web.Config file was updated.

Versions used but not limited to:
MySQL Server - 5.7.20
MySQL Connector/Net - 6.9.9
MySQL for Visual Studio - 1.2.7
Visual Studio 2017 Enterprise - 15.4.4
.NET Framework - 4.6.1
Nuget:
Entity.Framework - 6.2.0
MySQL.Data - 6.9.10
MySQL.Data.Entity - 6.9.10
MySQL.Web - 6.9.10
[15 Nov 2017 23:10] Matt Bilek
My comment should be:
I have also tried just about every workaround that has been posted on the internet with NO luck.
[16 Nov 2017 13:23] Chiranjeevi Battula
Hello MB,

Thank you for the bug report.
Verified this behavior on Visual Studio 2017 and MySQL Visual Studio 1.2.7 version.

Thanks,
Chiranjeevi.
[16 Nov 2017 16:30] Matt Bilek
Chiranjeevi,

Thanks for the confirmation.  Please let me know of the timing and ETA of when there will be a fix.  Patiently waiting...

Thank you,
Matt
[29 Nov 2017 10:12] Chiranjeevi Battula
http://bugs.mysql.com/bug.php?id=88683 marked as duplicate of this one.
[20 Jan 2018 21:38] Martin Diaz
Hi there, I'm not sure if it's kind of late but I just already deal with this problem:
1. Actually ADO works with MySQL Data Entity 6.9.10 in Visual Studio 201x
2. You should download Connector/NET 6.9.10 form MySQL website
3. It is not necessary to modify your web.config

I have this:
1. MySQL Server - 5.7.21
2. MySQL for Visual Studio 1.2.7
3. Connector/NET 6.9.10

Let me know.
[31 Mar 2018 16:32] Matt Bilek
Unfortunately need to have this work with Entity.Framework - 6.2.0.  Please view above notes.

As general practice, we should be able to use the combination of all latest releases with no restrictions, failure of backwards compatability, lack of functionality or even worse bugs and errors.

Sincerely,
Matt Bilek
[25 May 2018 16:28] Bari Tobi
Any new news on this one? I can confirm that this bug still exists despite version updates as can be seen below. The dialog window in Visual Studio just seem to crash according to the above description and there is no message in the output window what so ever. Is there a way a debug output somewhere in a file that can be found to bring some clarity in what goes wrong?  

My configurations displaying the latest stable versions of:
MySQL Server - 8.0.11
MySQL Connector/Net - 8.0.11
MySQL for Visual Studio - 1.2.8
Visual Studio 2017 Enterprise - 15.7.2
.NET Framework - 4.7.1
Nuget:
Entity.Framework - 6.2.0
MySQL.Data - 8.0.11
MySQL.Data.Entity - 6.10.7
[22 Oct 2018 19:11] Charles Peppler
I can confirm that this problem still exists.  I have spent days attempting
to find a way to make Entity framework in VS work with MySQL, and have also
tried multiple combinations of editions and releases to try and get it to work.
I had tried to get Oracle to help with their bug, but they ended up trying to 
sell me a service contract....to fix their own bug!

My configuration
MySQL Installer - 1.4.27.0
MySQL Server - 8.0.12
MySQL Connector/Net - 8.0.12
MySQL for Visual Studio - 1.2.8
Visual Studio 2017 Community - 15.8.7
.NET Framework - 4.6.1
Nuget:
Entity.Framework - 6.2.0
MySQL.Data - 6.10.8
MySQL.Data.Entity - 6.10.8