Skip to content
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

Open
ksysiekj opened this issue Jan 16, 2024 · 3 comments
Open

add new provider Microsoft.Data.SqlClient #69

ksysiekj opened this issue Jan 16, 2024 · 3 comments
Assignees

Comments

@ksysiekj
Copy link

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?

@JonathanMagnan JonathanMagnan self-assigned this Jan 16, 2024
@JonathanMagnan
Copy link
Member

Hello @ksysiekj

We might indeed consider supporting Microsoft.Data.SqlClient if we have a good reason.

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

@JonathanMagnan
Copy link
Member

Hello @ksysiekj,

Since our last conversation, we haven't heard from you.

Let me know if you need further assistance.

Best regards,

Jon

@AvremelM
Copy link

Speaking for myself:

One possible reason would be dotnet/announcements#292 (comment)

If you are using Microsoft.Data.SqlClient, anywhere (any version of .NET Framework or .NET) and you are using a version that is vulnerable you must update as listed in the affected packages.
If you are using the System.Data.SqlClient package from a .NET Framework (any version) application, you must install the January 2024 .NET Framework updates made available via Windows Update or Microsoft Update. You should also consider updating the System.Data.SqlClient package as keeping dependencies up to date is good general hygiene, but updating this package is neither necessary nor sufficient to fix the issue in a .NET Framework-based application.

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.


For which reason do you still prefer to use EF Classic over the official EF6 version?

EF6 still doesn't support targeting .NET Standard 2.0.
EF Classic does (and thank you for that!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants