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

Move to Microsoft.Data.SqlClient #15636

Closed
divega opened this issue May 6, 2019 · 4 comments · Fixed by #15761
Closed

Move to Microsoft.Data.SqlClient #15636

divega opened this issue May 6, 2019 · 4 comments · Fixed by #15761
Assignees
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Milestone

Comments

@divega
Copy link
Contributor

divega commented May 6, 2019

Now that the preview of Microsoft.Data.SqlClient is available in NuGet, we should be able to use it.

@ralmsdeveloper
Copy link
Contributor

@Tim-Bijnens
Copy link

Following this since we could realy use this to help port our current website to an Always Encrypted .Net Core app

@ajcvickers ajcvickers self-assigned this May 10, 2019
@ajcvickers ajcvickers added this to the 3.0.0 milestone May 10, 2019
ajcvickers added a commit that referenced this issue May 20, 2019
@ajcvickers ajcvickers added the closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. label May 20, 2019
@zenunits
Copy link

Waiting for Microsoft.Data.SqlClient to be integrated in preview of Microsoft.Entity.SqlServer. Currently its using System.Data.SqlClient as dependency.

Badly needed it to take advantage of column encryption feature of SQL Server 2016 in .net core project using entity core.

@ErikEJ
Copy link
Contributor

ErikEJ commented May 22, 2019

@kedarchinchvalkar @Tim-Bijnens You can use the new client with EF Core 2.x as described here: dotnet/SqlClient#11 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-fixed The issue has been fixed and is/will be included in the release indicated by the issue milestone. type-enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants