Currently EF Core 5.0 references v2.0.1 of Microsoft.Data.SqlClient that can cause some issues we recently addressed in v2.1.0:
Release Notes
Most important issues for EF users that were solved with v2.1.0:
InvalidOperationException and NotSupportedException errors due to WriteAsync collisions (important fix as impact was high) https://github.com/dotnet/SqlClient/issues/786#issuecomment-732278328 - fixed by https://github.com/dotnet/SqlClient/pull/796and many more bug fixes :)
Please update dependency on Microsoft.Data.SqlCLient to v2.1.0 when appropriate.
The short summary is:
@cheenamalhotra Done automatically already for 6.0: https://github.com/dotnet/efcore/pull/23434
We generally don't update to a new point release in a patch, but we will consider it if the issues fixed are significant.
@cheenamalhotra @ajcvickers How about EF Core 3.1? Will it switch to SqlClient 2.x on some point or will those fixes to be ported to SqlClient 1.x?
@olljanat You can just update to use 2.1.0 with EF Core 3.x: https://erikej.github.io/efcore/sqlclient/2020/03/22/update_mds.html
@ErikEJ but are those versions compatible? I assume that there is some breaking change which why version number was raised from 1.x to 2.x?
Yes, no breaking changes for EF Core
Discussed in triage. We will hold off on updating the dependency in 5.0.x for now to allow further feedback on the SqlClient 2.1, since it is newly released. We will then make a call as to whether or not to take this to Tactics.
Most helpful comment
@cheenamalhotra Done automatically already for 6.0: https://github.com/dotnet/efcore/pull/23434
We generally don't update to a new point release in a patch, but we will consider it if the issues fixed are significant.