You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Split Entity framework 6 provider from the FirebirdSql.Data.FirebirdClient.dll into a new DLL to avoid incompatibilties when using the DDEX Provider and trying to use EF6 in applications [DNET522]
#504
When you use the DDEX provider in Visual Studio you need to install the (non EF6) FirebirdSql.Data.FirebirdClient.dll into the GAC. When you now try to use EF6, the provider from the GAC (non EF6) is used all the time and this results in errors, because the EF6 requires new providers.
Solution:
Split Entity framework 6 provider from the FirebirdSql.Data.FirebirdClient.dll into a new DLL (maybe follow the Microsoft Naming convention what Microsoft does with their EG6 provider (EntityFramework.SqlServer) and name it EntityFramework.Firebird). Now the VS/DDEX can use the non EF6 version from GAC and EF6 projects can use the EntityFramework.Firebird without having issues.
The text was updated successfully, but these errors were encountered:
Submitted by: André Ziegler (andre.ziegler)
Is related to DNET503
Is duplicated by DNET554
Votes: 2
Problem:
When you use the DDEX provider in Visual Studio you need to install the (non EF6) FirebirdSql.Data.FirebirdClient.dll into the GAC. When you now try to use EF6, the provider from the GAC (non EF6) is used all the time and this results in errors, because the EF6 requires new providers.
Solution:
Split Entity framework 6 provider from the FirebirdSql.Data.FirebirdClient.dll into a new DLL (maybe follow the Microsoft Naming convention what Microsoft does with their EG6 provider (EntityFramework.SqlServer) and name it EntityFramework.Firebird). Now the VS/DDEX can use the non EF6 version from GAC and EF6 projects can use the EntityFramework.Firebird without having issues.
The text was updated successfully, but these errors were encountered: