-
Notifications
You must be signed in to change notification settings - Fork 282
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
Build conflict with SqlDbType #144
Comments
Looking at the locations for that type at https://apisof.net/catalog/System.Data.SqlDbType the only time it was present in S.D.SqlClient is the netstandard1.6+platform extensions. It shouldn't be present in any M.D.SqlClient builds as far as i can see. The answer might be to ensure that the project targets netstandard 2.0 or later and if it still preroduces the dependency resolution steps need to be checked. |
@Wraith2 have a look at my repro csproj! Looks like it is AppInsights package that pulls the dependency from a very old s.d.sqlclient |
It might be worth doing a build and then pulling the version of S.D.SqlClient that you find in the bin folder into a disassembler to see if it's a version that contains the type in question. If it is then in theory adding an explicit dependency to the latest version of S.D.SqlClient should force upgrade it. Dependency shenanigans can get messy though. |
@Wraith2 How would I do a build ? - this issue prevents building |
https://www.nuget.org/packages/System.Data.SqlClient/4.3.1 (.NET Standard 1.3!) |
Oh yeah... oops. Directly adding a reference to the latest (or later) S.D.SqlClient should cause the later version to be used instead of that transative one though. Without binding redirects i'm not sure what you'd have to do to resolve this i'm afraid. |
I think Wraith2's suggestion may work around it (add a newer reference yourself). But you probably need to file an issue in the Application Insights server repo and ask them to update the version they depend on since that old System.Data.SqlClient version is where the issue lies: |
Confirmed that adding a newer reference fixes the issue:
|
Closing issue here as issue identified with external library. |
A thread was started on an old EF Core issue that evolved into something which may be an issue with M.D.SqlClient, or should probably at least be investigated.
See dotnet/efcore#7820
Snippet of build output:
@slubowsky reported the issue, and @ErikEJ (one of our top contributors) has been able to reproduce it. I'm sure they will be wiling to help as needed if you need more information.
/cc @David-Engel @vickyharp @divega
The text was updated successfully, but these errors were encountered: