2

I want to use SqlHierarchId in my .net project but when I try to read a SqlHierarchId from DB, System.InvalidCastException will occur. I have written a simple code which it's accessible in bellow link, to show this problem:

SqlHierarchyIdTest

var connection = new SqlConnection("Data Source=.;Initial Catalog=tempdb;Integrated Security=True");
var val = connection.Query<Microsoft.SqlServer.Types.SqlHierarchyId>("select @Path", new {Path = Microsoft.SqlServer.Types.SqlHierarchyId.Parse("/1/2/3/")}).Single();

I trace code and reach the QueryImpl<T> in SqlMapper class. When Dapper tries to compare the type of value which is read by SqlDataReader, to the type of generic, confront two types of SqlHierarchyId!

Microsoft.SqlServer.Types

Fred
  • 3,365
  • 4
  • 36
  • 57
  • What does your connection string look like w.r.t. `TypeSystemVersion` https://msdn.microsoft.com/en-us/library/system.data.sqlclient.sqlconnectionstringbuilder.typesystemversion(v=vs.110).aspx – ta.speot.is Dec 24 '17 at 10:25
  • @ta.speot.is not work – Fred Dec 24 '17 at 11:05

1 Answers1

1

It looks as though one reference is bundled with the Dapper libraries, while the higher version is the one you installed or referenced from your machine.

Try add this to your app.config file to force all assemblies called Microsoft.SqlServer.Types to use the newest version:

<runtime>
  <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
    <dependentAssembly>
       <assemblyIdentity name="Microsoft.SqlServer.Types" publicKeyToken="89845dcd8080cc91" culture="neutral" />
       <bindingRedirect oldVersion="10.0.0.0" newVersion="14.0.0.0" />
    </dependentAssembly>
  </assemblyBinding>
</runtime>

Microsoft Docs on assembly redirects: Microsoft Docs - Redirecting Assembly Versions

SeanOB
  • 752
  • 5
  • 24