PowerShell 7.2 and 7.4 bundle deprecated Microsoft.Bcl.AsyncInterfaces 5.0.0.0 about powershell HOT 4 CLOSED

This is an unfortunate side effect of the fact that we have to pin the version of the System.ServiceModel.* packages to 4.10.x due to a breaking change in those packages with version 6.0.0 and above. See #19238 for details.

Mark this as "Engine-WG" for review.

from powershell.

@keithallenjackson For now, please consider using an AssemblyLoadContext to isolate your module, so that it will load the correct version of assembly for you. Please see https://github.com/daxian-dbw/PowerShell-ALC-Samples/tree/main/Resolving-Event-with-ALC if you are interested in doing so.

from powershell.

My current work project already utilizes an ALC, but it only works for non-foundational assemblies that are lazy loaded during runtime (sqlite as an example). It never even gets to the ALC logic for Bcl.AsyncInterfaces due to Bcl.AyncInterfaces being loaded before our assembly (and failing).

An important observation with #19238 is that ActiveDirectory loaded perfectly fine in 7.3.X, which included the correct Microsoft.Bcl.AsyncInterfaces version 7.0.0.0. As you can see from the import test results 7.3 does not have the import issue and it is because it includes the correct version as shown in the bcl library results

from powershell.

@keithallenjackson I didn't know that the v7.3.x ships with 7.0.0.0 Microsoft.Bcl.AsyncInterfaces.dll. If you look at the pwsh.deps.json in 7.2 and 7.4, you will find Microsoft.Bcl.AsyncInterfaces.dll is an indirect dependency pulled in by System.Private.ServiceModel.

However, by looking at the pwsh.deps.json for v7.3.11 (under the $PSHome folder), I found in v7.3 versions, the Microsoft.PowerShell.SDK.csproj has a direct reference to the v7.0.0 version of Microsoft.Bcl.AsyncInterfaces, but that direct dependency was removed in this PR: #19194 (see changes). Let me bring this to the team for discussion.

from powershell.