Dapper not fully compatible with Microsoft.SqlServer.Types 160.1000.6
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Hi!
First, and foremost, I've been using this library for years, and it's simply wonderful. Thank you, and the collaborators, for the hard work.
I just wanted to report that when I updated my project to Microsoft.SqlServer.Types 160.1000.6 (which is Dot Net Core compatible), SqlMapper.AddTypeHandler stopped working.
This particular code had been working flawlessly for years, up until today, when I decided to upgrade to NET 7, and Microsoft.SqlServer.Types 160.1000.6 to the most recent version.
Reverting to Microsoft.SqlServer.Types 14.0.1016.290 fixed the issue instantly.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing the reported failure with Dapper, .NET 7, and Microsoft.SqlServer.Types 160.1000.6, then compare it with version 14.0.1016.290 around SqlMapper.AddTypeHandler. Done means type-handler registration works with the newer package, with a regression test covering the compatibility issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100