Build conflict with SqlDbType
See original GitHub issueA 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 https://github.com/aspnet/EntityFrameworkCore/issues/7820
Snippet of build output:
1>Build FAILED.
1>
1>TVPBuilder.cs(48,29,48,38): error CS0433: The type 'SqlDbType' exists in both 'System.Data.Common, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' and 'System.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
1>Program.cs(13,92,13,101): error CS0433: The type 'SqlDbType' exists in both 'System.Data.Common, Version=4.2.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' and 'System.Data.SqlClient, Version=4.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
1> 0 Warning(s)
1> 2 Error(s)
1>
1>Time Elapsed 00:00:00.38
@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.
Issue Analytics
- State:
- Created 4 years ago
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Disadvantages of not specifying SqlDbType in ...
Question: what are potential problems or disadvantages that I might run into by not including the SqlDbType in the SQLCommand.Parameters?
Read more >Implement custom conflict resolver (Merge) - SQL Server
Build the project to create the custom conflict resolver library file. Deploy the library in the directory that contains the Merge Agent ...
Read more >Merging a Conflict with SQL Source Control and Beyond ...
Tony Davis explains how to resolve simple merge conflicts, such as conflicting changes to the same stored procedure, using SQL Source Control ...
Read more >Collation conflict when creating stored procedure
All you need to do is force a collation in that query via the COLLATE option/keyword. For example: ... [key] COLLATE ...
Read more >T-SQL- Error: “Cannot resolve the collation conflict between…”
The easiest solution is to use COLLATE DATABASE_DEFAULT on all character columns when creating your temp tables. This uses the collation already ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Confirmed that adding a newer reference fixes the issue:
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: https://github.com/microsoft/ApplicationInsights-dotnet-server/issues