-
Notifications
You must be signed in to change notification settings - Fork 289
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
Remove dependency on .NET Core internal shims #303
Comments
Eventually https://github.com/dotnet/corefx/issues/36896 will add a new .NET Core API that will provide for generating the Negotiate/NTLM tokens that SqlClient can use to do integrated authentication. But those new APIs will only be in .NET Core 5.0. So, since SqlClient probably builds against 'netstandard 2.0', perhaps it won't be able to take advantage of that. Or will have to ship its own copy of those new APIs and implementation when it is completed. |
We will consider discussing this offline with you, for clarifying approach.. |
Linking to issue dotnet/runtime#29270, which this one depends on. |
It doesn't actually depend on that. Such APIs would make this easier, but SqlClient can ship its own native shim with the library rather than depending on the private one in netcoreapp. |
Any progress here? I hit this issue when published a SingleFile app to a Docker container.
|
It looks like Microsoft.Data.SqlClient has a dependency on the .NET Core internal native shims on Unix. This needs to be removed.
https://github.com/dotnet/SqlClient/tree/master/src/Microsoft.Data.SqlClient/netcore/src/Common/src/Interop/Unix
It was a mistake for System.Data.SqlClient to take such a dependency, which is only valid for components in the .NET Core shared framework, not for NuGet packages that sit on top. These native libraries are private surface area that's subject to change from release to release, and any such change could easily break Microsoft.Data.SqlClient.
Assuming Microsoft.Data.SqlClient requires such functionality, it needs to ship its own native shims that it can version with its nuget package.
The text was updated successfully, but these errors were encountered: