Microsoft.Extensions.Caching.SqlServer is now using the new Microsoft.Data.SqlClient package

[jkotalik]

Microsoft.Extensions.Caching.SqlServer is now using the new Microsoft.Data.SqlClient package

The Microsoft.Extensions.Caching.SqlServer package will use the new Microsoft.Data.SqlClient package instead of System.Data.SqlClient package. This change could cause slight behavioral breaking changes. See https://devblogs.microsoft.com/dotnet/introducing-the-new-microsoftdatasqlclient/ for more information.

Version introduced

3.0

Old behavior

Prior to 3.0, the Microsoft.Extensions.Caching.SqlServer used the System.Data.SqlClient package.

New behavior

In 3.0 Microsoft.Extensions.Caching.SqlServer is now using Microsoft.Data.SqlClient.

Reason for change

Microsoft.Data.SqlClient is a new package that is built off of System.Data.SqlClient. It is where all new feature work will be done.

Recommended action

Customers shouldn't need to worry about this breaking change unless they were using types returned by the Microsoft.Extensions.Caching.SqlServer package and casting them to System.Data.SqlClient types. For example, if someone was casting a DbConnection to the old SqlConnection type, the would need to change the cast to the new Microsoft.Data.SqlClient.SqlConnection type.

Category

ASP.NET Core

Affected APIs

Not detectable via API analysis

---

Issue metadata

• Issue type: breaking-change