-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Method 'get_Info' in type 'MySql.Data.EntityFrameworkCore.Infraestructure.MySQLOptionsExtension' from assembly 'MySql.Data.EntityFrameworkCore' does not have an implementation #17788
Comments
The MySql provider must also be updated. |
I am already using the latest 8.0.17 according to https://www.nuget.org/packages/MySql.Data.EntityFrameworkCore/ |
But it must be updated for EF Core 3.0 due to breaking changes |
What do you mean? |
You would need to wait until the package author publishes a version which is compatible with EF Core 3.0. EF Core 3 is major release which contains breaking changes and each database provider need to react to it. Closing as this is external issue. Please contact the author of the package you are trying to use. |
I tried downgrade |
Share your csproj file. You need to use versions for 2.2 for all asp.net packages. Just downgrading EFCore package will not get you anything. |
Forget it. Too much unnecessary work. Either wait for donkey years before Oracle works it out or switch to PomeloFoundation/Pomelo.EntityFrameworkCore.MySql#797 |
We should downgrade from EFCore 3.0 to 2.2 ?? |
@ifew - You will need to wait for MySQL provider which works with EF Core 3.0. Till that is released, you would need to stick to version 2.2 |
has been reported here as well: |
THIS SUCKS!!!! |
Note that version 3.0 of the Pomelo MySQL provider has already been released, so this problem should no longer occur. If anyone is still running into issues, please open a new issue on the Pomelo repository. |
MySql.Data.EntityFrameworkCore release new version 8.0.19, The situation has not changed. |
@yasuoyuhao and others, just to clarify the current situation... There are two MySQL providers for Entity Framework Core:
In other words, if you want to use EF Core 3.0/3.1 with MySQL, at this point you need to use the Pomelo provider (or wait for the official MySQL one to get released). Note that neither of these are provided by the EF team or tracked by this repo - any bugs or feature requests must be filed directly with its respective project. |
try out these steps:
remember that Entity framework packages can be conflicts with other Entity framework packages so try one at a time and remove another because somtimes dot.net core provide preinstalled EntityFramework.Core.SqlServer |
This is listed as the official package on Microsoft's site: https://www.nuget.org/packages/Pomelo.EntityFrameworkCore.MySql |
@scubakiz Can you point to where this is linked as an "official package"? |
This is Microsoft's list of Database Providers for .Net Core: https://docs.microsoft.com/en-us/ef/core/providers/?tabs=dotnet-core-cli There are multiple options for MySQL available. |
@scubakiz That doesn't indicate in any way that those packages are "official". They are just the packages that people have told us about. Hence:
That being said, the Pomelo MySQL provider seems very good to me. It's just not officially endorsed in any way by Microsoft. |
Same error.
Still no updated version for 3.0. |
Suffering the same problem |
For anybody coming to this issue, please read this comment above explaining the situation. Long story short, the EF Core team is not the maintainer of MySql.Data.EntityFrameworkCore - please communicate with them about releasing a newer version of their provider which supports EF Core 3.1. As an alternative, consider switching to Pomelo.EntityFrameworkCore.MySql which is a full-featured EF Core MySQL provider supporting 3.1 (also not maintained by this team). Posting further comments here won't help the situation in any way... |
Thanks for the information @roji |
Below is the screenshot from the bug - https://bugs.mysql.com/bug.php?id=96990 And MySql.Data 8.0.20 is released on 27 April 2020 |
I have upgraded the SDK and runtime to 3.0, upgraded the packages in .csproj but bump into the exception:
Notice the spelling error in the namespace,
Infraestructure
instead ofInfrastructure
. Could that be the root cause?Steps to reproduce
Further technical details
EF Core version: 3.0
Database provider: (e.g. Microsoft.EntityFrameworkCore.SqlServer)
MySql.Data.EntityFrameworkCore
Target framework: .NET Core 3.0
Operating system: Ubuntu 19.04
IDE: Visual Studio Code 1.38.1
The text was updated successfully, but these errors were encountered: