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
Microsoft.Data.SqlClient epic #1490
Comments
Do the regrets have something to do with this issue or are they unrelated? |
Interesting. @mattbrailsford I wonder if the SNI issue with SQLite is related to this issue? @PeterBenko Matt had to manually include the SQLite native interface package in his recent PR. |
@PeterBenko I think I found the root cause, which wasn't really articulated in that issue you linked, but hinted at: It looks like this document explains it: https://docs.microsoft.com/en-us/sql/connect/ado-net/sqlclient-troubleshooting-guide?view=sql-server-ver15
Our tests run on net461: I believe @mattbrailsford ran into a similar issue, and his fix was to force a PackageReference to the package containing the missing dll. Note, it seems nuget restore for legacy .NET Framework can restore these native dlls, it just can't do it as a transitive reference, apparently. |
It seems like the 3.2.16 release decision to move to Microsoft.Data.SqlClient may have been a regretful one. Initially it was only Mono users impacted by this problem, but now it appears to be more general.
#1483 -- @arhughes
#1486 -- @m4rkyx
The text was updated successfully, but these errors were encountered: