Bug #98325 VS 2019 Entity Data Model Wizard crashes
Submitted: 22 Jan 2020 11:04 Modified: 18 Mar 2020 8:10
Reporter: Nicolò De Paoli Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Visual Studio Integration Severity:S2 (Serious)
Version:8.0.19 OS:Windows
Assigned to: CPU Architecture:Any

[22 Jan 2020 11:04] Nicolò De Paoli
Description:
In Visual Studio 2019 can't add an ADO.NET Entity Data Model because the Entity Data Model Wizard crashes after selecting the connection and clicking "Next" button.

How to repeat:
- Install Visual Studio Community 2019 Version 16.4.3
- Install MySql Connector/NET 8.0.19
- Install MySql for Visual Studio 1.2.9
- Create a Console Application (.NET Framework 4.7.2)
- Add MySql.Data nuget package version 8.0.19
- Add MySql.Data.Entity nuget package version 6.10.9

- Set the app.config like this:

<connectionStrings>
  <add name="MySqlConnection" providerName="MySql.Data.MySqlClient" connectionString="server=myserver;port=3306;database=mydb;uid=myuser;password=mypwd" />
</connectionStrings>
<entityFramework>
  <defaultConnectionFactory type="System.Data.Entity.Infrastructure.SqlConnectionFactory, EntityFramework"/>
  <providers>
    <provider invariantName="MySql.Data.MySqlClient" type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.Entity.EF6"/>
    <provider invariantName="System.Data.SqlClient" type="System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer"/>
  </providers>
</entityFramework>
<system.data>
  <DbProviderFactories>
    <remove invariant="MySql.Data.MySqlClient" />
    <add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=8.0.19.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" />
  </DbProviderFactories>
</system.data>

- Try to add an ADO.NET Entity Data Model, it always crashes after selecting the Data Connection
[18 Mar 2020 6:41] MySQL Verification Team
Hello Nicolò De Paoli,

Thank you for the bug report.
Imho this is duplicate of Bug #88507, please see Bug #88507.

Regards,
Ashwini Patil
[18 Mar 2020 8:10] Nicolò De Paoli
It's the same behavior but with different versions of VS and .NET connector. Is there any solution or workaround for VS2019?
[9 Apr 2020 15:52] Jose Longo
Same beavior here with last versions of conector/vs...
Any workarround or solution ?
[9 Aug 2020 6:25] Hanan Schwartzberg
Still having the same problem. Any one have an update?
[4 Mar 2021 14:02] Arman Khody
I always have to downgrade to 6.8.8 to update my models and then back to 8.0.xx 
I don't know how others can use he wizard and don't complain.
I tested every possible mix and they don't work.
Also tested on 
Visual Stdio 2015 Pro
Visual Stdio 2015 Enterprise
Visual Stdio 2017 Enterprise

Only Nuget 6.8.8 works for me on 2015/2017

(Also tested 8.0.17, doesn't work either!)
[24 Aug 2021 13:21] Hanan Schwartzberg
I tried that, but it just results in the connection not showing as one of the options and MYSql not being an option for a new connection.