GeezerVison

It looks like this is a transitive dependency of System.ServiceModel.NetTcp. The PR PowerShell/PowerShell@e069c1d updated System.ServiceModel.NetTcp to a newer version which brought in the transitive dependency of System.ServiceModel.NetFramingBase but as that was never added to the TPA it would fail to be loaded.

I have not verified but this seems to be a regression with 7.6.0 which is when the updated assembly was introduced. While not ideal, a workaround for people using Enter-PSSession to a PowerShell 7 based endpoint is to run this before importing the module

Add-Type -Path "$PSHome\System.ServiceModel.NetFramingBase.dll"

For people relying on JEA with a restricted language mode you can achieve the same thign automatically by adding this to your session configuration (.pssc) file:

@{
    ...
    AssembliesToLoad = @(
        "$PSHome\System.ServiceModel.NetFramingBase.dll"
    )
}

Thanks for raising this! Hopefully it lands soon 🙏

I was testing AssembliesToLoad in the .pssc and I think $PSHome is unnecessary. As long as the entry ends with .dll then GetFileNameWithoutExtension is eventually called on it:
https://github.com/PowerShell/PowerShell/blob/master/src/System.Management.Automation/engine/ExecutionContext.cs#L1419

GitHub

PowerShell/src/System.Management.Automation/engine/ExecutionContext.cs at master · PowerShell/PowerShell

PowerShell for every system! Contribute to PowerShell/PowerShell development by creating an account on GitHub.

Thanks, I mostly added the $PSHome to remove any ambiguity and tell PowerShell to always use the dll shipped by that PowerShell version and not anything else that may be found in the environment.

Erm what I mean is AssembliesToLoad = @("https://google.com/obviously-this-does-not-exist/System.ServiceModel.NetFramingBase.dll") works just as well i.e. I don't think variables are being expanded or that anything else in those strings matter except for the filename.

Ah I see, sorry I misread your post.

Similarly JsonSchema.Net should also be added (noticed that Test-Json '[]' doesn't work even in 7.4)

Jordan Borean (@jborean93) Thank you for finding the root cause of PowerShell/PowerShell#27907.
There are lots of mismatches because the TPA list hasn't been updated for a very long time. Also, the TPA assemblies for 7.4, 7.5, and 7.6 versions are not the same. #115 changes from an allow-list to a deny-list, so the TPA used by pwrshplugin.dll will only include the correct TPA assemblies for that specific version.