protobuf-net-data dependency with System.Memory

[hakanornek]

I was using protobuf-net-data 4.0.0 in my project. While everything was working fine in .NET Framework 4.7.2, When Update System.Memory 4.6.2 from NuGet package i have an exception like this ;

Exception thrown: 'System.IO.FileLoadException' in protobuf-net-data.dll ("Could not load file or assembly 'System.Memory, Version=4.0.2.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference.

System.Memory Working: 4.6.0 ✔ Not Working : 4.6.2 😢
System.Buffers Working: 4.6.0 ✔ Not Working : 4.6.1 😢
System.Numerics.Vectors Working: 4.6.0 ✔ Not Working : 4.6.1 😢

Thanks for your helps..

[dotarj]

It looks like you need to add a binding redirect to your web.config or app.config. Usually, NuGet adds or updates binding redirects itself, but somehow it didn't.

I created a new .NET Framework 4.7.2 solution and installed protobuf-net-data, and after that updated System.Memory to version 4.6.2. Everything worked perfectly as NuGet automatically added this app.config with these assembly redirects:

<?xml version="1.0" encoding="utf-8"?><configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-4.0.4.0" newVersion="4.0.4.0" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-6.0.2.0" newVersion="6.0.2.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

Please keep in mind that binding redirects use the assembly file versions, not the NuGet versions.

You can find more information on binding redirects here: https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions.

[hakanornek]

Hi Arjen, I solved my problem with binding redirect. Thank you very much for your valuable help... Best Regards. Hakan

…

On Mon, Mar 24, 2025 at 10:23 AM Arjen Post ***@***.***> wrote: It looks like you need to add a binding redirect to your web.config or app.config. Usually, NuGet adds or updates binding redirects itself, but somehow it didn't. I created a new .NET Framework 4.7.2 solution and installed protobuf-net-data, and after that updated System.Memory to version 4.6.2. Everything worked perfectly as NuGet automatically added this app.config with these assembly redirects: <?xml version="1.0" encoding="utf-8"?><configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-4.0.4.0" newVersion="4.0.4.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-6.0.2.0" newVersion="6.0.2.0" /> </dependentAssembly> </assemblyBinding> </runtime> </configuration> You can find more information on binding redirects here: https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions . — Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSQDH5PXHDEOJ6RHJTR7N32V6XF5AVCNFSM6AAAAABZSE4DECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBXGEYTQNZWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***> [image: dotarj]*dotarj* left a comment (dotarj/protobuf-net-data#75) <#75 (comment)> It looks like you need to add a binding redirect to your web.config or app.config. Usually, NuGet adds or updates binding redirects itself, but somehow it didn't. I created a new .NET Framework 4.7.2 solution and installed protobuf-net-data, and after that updated System.Memory to version 4.6.2. Everything worked perfectly as NuGet automatically added this app.config with these assembly redirects: <?xml version="1.0" encoding="utf-8"?><configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="System.Buffers" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-4.0.5.0" newVersion="4.0.5.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Memory" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-4.0.4.0" newVersion="4.0.4.0" /> </dependentAssembly> <dependentAssembly> <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-6.0.2.0" newVersion="6.0.2.0" /> </dependentAssembly> </assemblyBinding> </runtime> </configuration> You can find more information on binding redirects here: https://learn.microsoft.com/en-us/dotnet/framework/configure-apps/redirect-assembly-versions . — Reply to this email directly, view it on GitHub <#75 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACSQDH5PXHDEOJ6RHJTR7N32V6XF5AVCNFSM6AAAAABZSE4DECVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDONBXGEYTQNZWGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- Hakan ORNEK Ms.Civil Eng.