Skip to content

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

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

Closed
jkotalik opened this issue Sep 30, 2019 · 0 comments · Fixed by #15044
Closed
Assignees
Labels
breaking-change Indicates a .NET Core breaking change

Comments

@jkotalik
Copy link
Contributor

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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
breaking-change Indicates a .NET Core breaking change
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants