issue with Microsoft.Extensions.Logging.Abstractions. Any help?

[trsbriank]

Hi there, Would someone be able to help me resolve this issue? I am targeting a project (plugin dll) with .NET Framework 4.8.
My main program is now on the latest version of Microsoft.Extensions.Logging.Abstractions which is 9.0.9.
When I attempt to use the SSH.NET library, I get the following error:
Could not load file or assembly 'Microsoft.Extensions.Logging.Abstractions, Version=8.0.0.3, Culture=neutral, PublicKeyToken=adb9793829ddae60' or one of its dependencies. The system cannot find the file specified. at Renci.SshNet.ServiceFactory..ctor()

However, nuGet and all the relevant documentation says that 8.0.0.3 is only the minimum version required by SSH.NET,
so why would this happen?
If I use a binding redirect, I get this compile warning and it still causes an error

warning MSB3277: "Microsoft.Extensions.Logging.Abstractions, Version=8.0.0.3, Culture=neutral, PublicKeyToken=adb9793829ddae60" was chosen because it was primary and "Microsoft.Extensions.Logging.Abstractions, Version=9.0.0.9, Culture=neutral, PublicKeyToken=adb9793829ddae60" was not.

Thank you so much. this library is great!

[Rob-Hague]

What do your binding redirects look like? Are they on the main program, or the plugin? Not an expert on this

[trsbriank]

oops, somehow missed the notification for this response.
These are my binding redirects for the plugin. I don't have any for my main program

<?xml version="1.0" encoding="utf-8" ?> <configuration> <runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Microsoft.Bcl.AsyncInterfaces" publicKeyToken="cc7b13ffcd2ddd51" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-8.0.0.0" newVersion="8.0.0.0" /> </dependentAssembly> </assemblyBinding> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Microsoft.Extensions.Logging.Abstractions" publicKeyToken="adb9793829ddae60" culture="neutral" /> <bindingRedirect oldVersion="0.0.0.0-9.0.0.10" newVersion="9.0.0.10" /> </dependentAssembly> </assemblyBinding> </runtime> </configuration>

[mus65]

Binding redirects need to be defined on the application project, they have no effect when defined on libraries.

[trsbriank]

thanks for explaining. Because I don't understand what is happening, I was trying anything I could think of. I really need to be able to solve this at the plugin level. This only happened after I upgraded from version 2023.0.1

[mus65]

You can't solve this at the plugin level. The application must deal with binding redirects because it is the only one that knows all its dependencies. If the application e.g. actually needs Microsoft.Extensions.Logging.Abstractions 10.0.0 (because another dependency pulls it in), the binding redirect of your plugin would not even make sense. Only the application knows that it must actually redirect to version 10.0.0, not to 9.0.0.

Most modern applications automatically generate binding redirects. Afaik the only case where you still must maintain binding redirects manually are legacy ASP .NET Framework web applications.

This is also not an SSH.NET specific issue. A lot of transitive dependencies of other nuget package will need binding redirects in an application.

[trsbriank]

My application is set to automatically generate binding redirects. I use many different 3rd party libraries that I have upgraded and I have only encountered this issue after upgrading SSH.NET, so I do think this issue is specific to this library.

[mus65]

I don't see what SSH.NET could do wrong here, it simply references Microsoft.Extensions.Logging.Abstractions. SSH.NET probaby just happens to trigger the issue for you because of your and its own specific dependencies.

If you automatically generate your binding redirects, there must be something else going on. Can you provide a minimal repro?

[trsbriank]

I certainly don't think there's anything wrong with SSH.NET at all. I was hoping there would be a clue in that this issue only happened after upgrading from 2023.0.1, or that perhaps someone else had seen this error before to even give me a direction to look in. I've been coding in this environment for over 15 years and I've never been so stumped before!