Can't Create Entity Data Model - using MySql a

问题:

I'm trying to add an edmx Entity model to my C#/Web Project in Visual Studio 2013. My problem is that the file is not created.

I do the following steps:

1. Give the item a name
2. Choose 'EF Designer from database'
3. Choose the connection from the drop down (localhost) that already tested successfully connecting to MySQL databse
4. The "Save connection settings in webc.config as" option is checked
5. I click 'Next' AND the window disappeared and I get back to the code window

No edmx file is created. (although it works with SQL Server, but not for MySQL)

I have Entity Framework 6.1.2 installed, MySql.Data, MySql.Data.Entities, MySql.Data.Entity, MySql.Web -- all installed.

I also rebuilt the project before trying to add an entity model file.

I've installed the latest MySQL package with the latest .NET connector.

Running: Visual Studio 2013 on Windows 7.

Any ideas how to solve this?

回答1:

I solved this issue by following some steps below:

1. Uninstall MySql.Data.Entities from Nuget by using command below in Package Manager Console: Uninstall-Package MySql.Data.Entities

2. Add project reference to the latest MySql.Data.Entity.EF6.dll from your MySql connector installation path at: C:\Program Files (x86)\MySQL\MySQL Connector Net 6.9.8\Assemblies\v4.5

回答2:

I just had the same situation when trying to configure Visual Studio Professional 2017 environment with MySQL, ADO.NET (Database First) and EF6.

Note: Please follow steps in the same order.

1. Uninstall/remove "Connector/NET" and "MySQL for Visual Studio" if installed.

2. Install "MySQL for Visual Studio" v2.0.5 CTP (MySQL for Visual Studio). Note: Install MySQL for Visual Studio before Connector/NET.

3. Install "Connector/NET" v6.9.10 (Connector/Net). https://i.stack.imgur.com/XOT1I.jpg Note: I tried using Connector/NET v6.8, v6.10 and v8 first, but none of them worked with Visual Studio 2017 and ADO.Net. Here you can find all Connector Versions and Compatibilities with Visual Studio IDEs, but so far this list is inaccurate.

4. Create new Visual Studio Professional 2017 project.

5. Download and Install "EntityFramework" v6.2.0 through NuGet, by going to Project Tab/Manage NuGet Packages/Browse -> Entity Framework.

6. Add references to C:\Program Files (x86)\MySQL\Connector.NET 6.9.10\Assemblies\v4.5\MySql.Data.dll and C:\Program Files (x86)\MySQL\Connector.NET 6.9.10\Assemblies\v4.5\MySql.Data.Entity.EF6.dll; by Right Clicking over References inside Solution Explorer and selecting Add Reference/Browse ->Browse button.

7. Add MySQL EF6 provider info inside App.config under entity framework providers as follow:

<entityFramework>
       <providers>
         <provider invariantName="MySql.Data.MySqlClient"
              type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.Entity.EF6" />
       </providers>
</entityFramework>

8. Rebuild project by going to Build tab/Rebuild ProjectName.

And that's it. VS2017 is ready to go. Hope this works for everybody, as it did for me today.

References:

1. Can't Create Entity Data Model - using MySql and EF6

2. No Entity Framework provider found for 'MySql.Data.MySqlClient' ADO.NET provider

回答3:

VS 2015 still has this bug. It is caused by version mismatch.

On my system, I had MySQL Connector 6.9.6.
Issuing the command in NuGet Package Manger Console:

Install-Package MySql.Data.Entity

installs version 6.9.8 by default. Your connector must match the actual version of the NuGet Package.
You can download an updated version of the connector from: https://www.mysql.com/products/connector/

Here select the "Ado.net driver for MySQL", and download the corresponding version (in this case 6.9.8). Reopen Visual Studio and now the wizard does not crash. No reboot required.

回答4:

I was able to resolve this problem by performing the following:

1. Open MySQL Installer and install the latest version of Connector/NET
2. Uninstall / reinstall the latest version MySQL.Data.* packages with versions that match the version of the newly installed Connector/NET package
3. Restart Visual Studios
4. Rebuild solution

回答5:

Taking suggestions about NuGet versioning from others answers. I solved this issue by deleting the .Data and Data.Entitiy.EF6 installed by Nuget.

Then right click on References and browse for:

C:\Program Files (x86)\MySQL\Connector.NET 6.9\Assemblies\v4.5\MySql.Data.dll and C:\Program Files (x86)\MySQL\Connector.NET 6.9\Assemblies\v4.5\MySql.Data.Entity.EF6.dll

I was then able to complete the ADO.Net wizard, with the .edmx models.

回答6:

I know the solution.

Nuget installs edge version of MySql.Data.* packages, while you probably have previous version of the connector (In my case packages were v. 6.9.6 and Connector was 6.9.5). This comes to the point where you have version mismatch.

Be aware that if you use Install-Package MySql.Data.Entities in NuGet you will get even older version like 6.8.3, so you have to add the references by yourself and keep an eye on which one you are trying to add to your solution.

回答7:

I had the same problem using MySQL Connector 6.9.8.0. While all my versions matched, this still failed. I had installed a new version of Visual Studio AFTER the MySQL connector (From 2010 to 2013). For me, the solution was to uninstall the MySQL Connector for NET and then reinstall it (Exact same version). Then restart Visual Studio.

Seems like this is another version of the same problem.

回答8:

You can do this solution:

1. Add a new empty EF model.
2. In the emdx design rigth click and update the model from database.
3. choose your database and the model will be generate.

That's work for me :)

回答9:

another thing to try:

--->install the entityframework 6.2.0 via nuget.

--->Verify in your web.config/app.config file that you have the System.Data.SqlServerCe.4.0 provider. if it's not installed, then install it via nuget, the exact same version as the entity framework previously installed (6.2.0 in this case).

--->then add the references: (in this case from the connector/NET version 6.9.10) C:\Program Files (x86)\MySQL\Connector.NET 6.9\Assemblies\v4.5\MySql.Data.dll and C:\Program Files (x86)\MySQL\Connector.NET 6.9\Assemblies\v4.5\MySql.Data.Entity.EF6.dll and rebuild.

--->try adding this provider too: <provider invariantName="MySql.Data.MySqlClient" type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.Entity.EF6" /> rebuild, again.

--->and finally, try adding the .edmx file with a new connection.

This worked in my case where i installed VS2017 and MySQL in a brand new laptop, and had the same issue.

回答10:

I changed my web.config file from:

<provider invariantName="MySql.Data.MySqlClient" type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.EntityFramework, Version=8.0.11.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d" />

To:

<provider invariantName="MySql.Data.MySqlClient" type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.Entity.EF6"></provider>

回答11:

This is for an ASP.NET MVC application, which does not have an app.config file. I will not recount the failed attempts, but what worked for me was the following:-

• With VS not running, download and install "MySQL for Visual Studio 2.0.5" - the latest version at time of writing.
• Start VS2017 and uninstall the "MySql.Data.Entity" and "MySql.Data" NuGet packages, if they have been previously installed in VS2017.
• Download and install the latest MySql connector/NET using the links above (version 8.0.13 at time of writing).
• In your project add references to the "MySql.Data.dll" and "MySql.Data.EntityFramework.dll" dlls as described above by Lopez93, but N.B. the "MySql.Data.Entity.EF6.dll" mentioned did not exist in 8.0.13, only "MySql.Data.EntityFramework.dll".
• Now edit the web.config file and make sure that in the section, there is this line

<provider invariantName="MySql.Data.MySqlClient" type="MySql.Data.MySqlClient.MySqlProviderServices, MySql.Data.EntityFramework">

• Remove or comment out any other '<provider invariantName="MySql.Data.MySqlClient"...' lines.

• Rebuild the project.

Try using the wizard again.

For me this worked.

Good luck!