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
Failing to connect to Firebird from EF Core 3 [DNET902] #829
Comments
Modified by: @cincuranetComponent: http://ADO.NET Provider [ 10041 ] => Component: NuGet packages [ 10150 ] => |
Commented by: @cincuranet Please provide a small reproducible test-case and/or exact versions you're using. |
Commented by: Gerdus van Zyl (angelblaze) This is the error you get when running on EntityFrameworkCore version 3.0; while the firebird provider supports currently 2.2 |
Commented by: John Greco (jfgreco) Correct. Any application in .net Core 3 that tries to connect to Firebird has this error. |
Commented by: @cincuranet Thanks Gerdus, that was my guess, so I asked for the versions. The EFCore 3 support is tracked in DNET903, so I'll close this. |
Modified by: @cincuranetsummary: Failing to connect to Firebird => Failing to connect to Firebird from EF Core 3 |
Commented by: Valdir Stiebe Junior (ogecrom) As a workaround, we made it work with entity framework core 3.1 removing the following PackageReference from our project.csproj. <PackageReference Include="Microsoft.EntityFrameworkCore.Sqlite" Version="3.1.0" /> |
I'm having this same issue with: Application .Net 5.0 Console Application |
Assembly EntityFrameworkCore.FirebirdSql is not this provider. |
Submitted by: John Greco (jfgreco)
Trying to utilize: services.AddDbContext<SheaDbContext>(options => options.UseFirebird(connectionString));
Raises an exception:
"Method 'get_Info' in type 'FirebirdSql.EntityFrameworkCore.Firebird.Infrastructure.Internal.FbOptionsExtension' from assembly 'FirebirdSql.EntityFrameworkCore.Firebird, Version=7.1.1.0, Culture=neutral, PublicKeyToken=7a73ef09980c56c9' does not have an implementation." string
The text was updated successfully, but these errors were encountered: