-
Notifications
You must be signed in to change notification settings - Fork 28
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
add new provider Microsoft.Data.SqlClient #69
Comments
Hello @ksysiekj We might indeed consider supporting Previously, the major reason people were using EF Classic was that our library was the only one supporting it NET Core but that's not true anymore, EF6 itself has supported .NET Core since the v6.3 For which reason do you still prefer to use EF Classic over the official EF6 version? Most added features on EF Classic are also available when using Entity Framework Extensions and Entity Framework Plus Best Regards, Jon |
Hello @ksysiekj, Since our last conversation, we haven't heard from you. Let me know if you need further assistance. Best regards, Jon |
Speaking for myself: One possible reason would be dotnet/announcements#292 (comment)
Using System.Data.SqlClient on .NET Framework requires a Windows Update to fix the security issue. Depending on Microsoft.Data.SqlClient would allow consumers to fix the issue merely by using an updated package.
EF6 still doesn't support targeting .NET Standard 2.0. |
Can you upgrade System.data.sqlclient to 4.8.6 which resolved this CVE : https://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-0056 |
hello,
Based on dotnet/ef6#2063 - are you planning to add support for the new provider type base on Microsoft.Data.SqlClient once EF 6.5 is released?
The text was updated successfully, but these errors were encountered: