-
Notifications
You must be signed in to change notification settings - Fork 612
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
Consider using Microsoft.Data.SqlClient instead of System.Data.SqlClient in MsSqlDataConnection #528
Comments
Thanks for the idea. Is the new SqlClient fully compatible with the old SqlClient? I think we need to add new plugin with other name for minimize user's errors but I have no idea what the new plugin will be called and maybe we really need to replace it. |
It is compatible. Plus it supports more connection string formats |
Like @MaximBalaganskiy said, it is compatible but I just want to point out that Microsoft.Data.SqlClient has a breaking change, the Encryption is now On by Default. |
Hello! Microsoft.Data.SqlClient instead of System.Data.SqlClient is planned in the next release, expect changes Best regards, |
Any progress on this? |
@BogdanStegachev Please reopen, this is not resolved |
Hello! At the moment the replacement of Microsoft.Data.SqlClient instead of System.Data.SqlClient is not completed, as soon as there are changes we will immediately inform you in this issue Best regards, |
Is your feature request related to a problem? Please describe.
Azure Managed Identity connection strings are not supported in
System.Data.SqlClient.SqlConnection
Describe the solution you'd like
Return
Microsoft.Data.SqlClient.SqlConnection
fromGetConnectionType
Describe alternatives you've considered
The alternative is to create a custom FR connection
Additional context
See https://devblogs.microsoft.com/dotnet/introducing-the-new-microsoftdatasqlclient/
The text was updated successfully, but these errors were encountered: