Question: Dapper / Dapper.StrongName dependency

Question

Question: Dapper / Dapper.StrongName dependency

AkosLukacs opened this issue 6 years ago · 9 comments

Hi!

Latest MiniProfiler.Providers.SqlServer depends on Dapper.StrongName package, this package depends on Dapper package.
Any idea how to solve this now, or plans to change the dependency of this package to Dapper.StrongName?

Thanks!

Answer 1 · 2018-08-17T11:46:27.000Z

Same here, I get:

Error CS0121 The call is ambiguous between the following methods or properties: 'Dapper.SqlMapper.AsList(System.Collections.Generic.IEnumerable)' and 'Dapper.SqlMapper.AsList(System.Collections.Generic.IEnumerable)'

when I'm trying to use .AsList(), for instance, because both Dapper and Dapper.StongName are referenced.

@AkosLukacs Did you solve it?

Answer 2 · 2018-08-17T11:48:16.000Z

Just rolled back to previous version :( Nicholaos Bilalis <notifications@github.com> ezt írta (időpont: 2018. aug. 17., P 13:46):

…

Same here, I get: Error CS0121 The call is ambiguous between the following methods or properties: 'Dapper.SqlMapper.AsList(System.Collections.Generic.IEnumerable)' and 'Dapper.SqlMapper.AsList(System.Collections.Generic.IEnumerable)' when I'm trying to use .AsList(), for instance, because both Dapper and Dapper.StongName are referenced. @AkosLukacs <https://github.com/AkosLukacs> Did you solved it? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#136 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAziKzfucvs5gAosBXKEUI4xXthP3Lb4ks5uRq0WgaJpZM4U5p3-> .

Answer 3 · 2018-08-17T12:48:36.000Z

Hey @AkosLukacs , I found a solution that worked for me. I added the following to my .csproj:

  <Target Name="ChangeAliasesOfStrongNameAssemblies" BeforeTargets="FindReferenceAssembliesForReferences;ResolveReferences">
    <ItemGroup>
      <ReferencePath Condition="'%(FileName)' == 'Dapper.StrongName'">
        <Aliases>SomeAlias</Aliases>
      </ReferencePath>
    </ItemGroup>
  </Target>

Answer 4 · 2019-03-02T13:09:24.000Z

Dapper v2 will do away with strong name (the only real solution for this...it's just a big one), but that will be later this year at the earliest. We've been busier than expected and StackExchange.Redis ate a lot more of our v2 time than we planned on. It's next on our list, though.

Tagged this as blocked for now to I keep an eye on it. As soon as we release Dapper v2, I'll release a new exceptional with the dependency to unblock upgrades and the scenario here.

Answer 5 · 2019-04-10T20:39:52.000Z

Thanks @lalibi, your solution is just what I've looked for.

Answer 6 · 2019-10-24T14:41:43.000Z

Is this now possible with the Dapper 2 release?

Answer 7 · 2021-05-08T04:06:23.000Z

Looks MiniProfiler is still referencing Dapper.StrongName, which is not a popular nuget package at all. Instead, Dapper is the primary release. This makes it impossible for Dapper (not Dapper.StrongName) users to use MiniProfiler at all if they need to use MiniProfiler.Providers.XXX.

Answer 8 · 2021-05-21T20:19:02.000Z

Anybody finding the same issue: @lalibi 's workaround does work, thanks for sharing!

Answer 9 · 2024-05-16T18:39:25.000Z

This workaround with alias helped me in 2024 :) Thanks!