2023.0.1 requires exact Microsoft.Bcl.AsyncInterfaces version

[mus65]

I noticed that #1268 introduced a dependency to an exact version of Microsoft.Bcl.AsyncInterfaces (8.0.0) . I assume this was a copy&paste mistake from the SshNet.Security.Cryptography dependency. Please changes this to a minimum version (>= 8.0.0), otherwise projects using SSH.NET will run into issues when trying to upgrade to a newer Microsoft.Bcl.AsyncInterfaces release.

[darkoperator]

seems I hit an issue with this in Posh-SSH

[mus65]

@darkoperator doesn't look like the same issue. This issue is about the too strict version constraint which would cause nuget restore failures if other projects depend on another Microsoft.Bcl.AsyncInterfaces version. Your issue seems to be about the dependency itself missing.

[darkoperator]

ok, sadly my module is broken because of this dependency on PS 7, it is one weird bug I can not figure out so sticking with the previous nugget for now

[mus65]

Fixed by #1288

[WojciechNagorski]

This issue has been fixed in the 2024.0.0 version.

[ThatBrianK]

Hi, I just wanted to chime in and say that this fix actually broke the library I had built. I now get an error:

Could not load file or assembly 'Microsoft.Bcl.AsyncInterfaces, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or
one of its dependencies. The system cannot find the file specified.

I do not get this error with 2023.0.1 but with any higher version I do. I tried 2 tricks I could find online but neither of them worked.

1. check "auto-generate binding redirects
2. adding an App.config file containing the following:
   <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>

I'm not really sure where to go for help. Thanks!

[mus65]

This does indeed look like missing binding redirects. There is no text on 2. , did you forget to paste it?

The fix depends on your application. For modern .NET, the binding redirects should always be automatically generated unless you explicitly disable them. For legacy .NET framework it can be more complicated.

[ThatBrianK]

thanks, I forgot to enclose it as Code.
I'm using .NET Framework 4.8.
<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>