We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
dotnet/SqlClient#727 can cause issues for people using DistributedLock 2.0 in .NET framework executables.
Might be good to call this out explicitly in the docs to head off questions.
Also could be worth considering an API that takes in DbProviderFactory so that someone can easily opt back into System.Data.SqlClient.
DbProviderFactory
The text was updated successfully, but these errors were encountered:
Such a nasty issue this one. We're running into it from today 🎉
Sorry, something went wrong.
No branches or pull requests
dotnet/SqlClient#727 can cause issues for people using DistributedLock 2.0 in .NET framework executables.
Might be good to call this out explicitly in the docs to head off questions.
Also could be worth considering an API that takes in
DbProviderFactory
so that someone can easily opt back into System.Data.SqlClient.The text was updated successfully, but these errors were encountered: