Document Asp.Net Core 5.0 behavior on BinaryFormatter with Microsoft.PowerShell.SDK

[fMichaleczek]

Summary of the new document or enhancement

• Link(s) to related issue(s) in the PowerShell/PowerShell repo: #14032

Description of what changed

Starting net5.0, if you use the PowerShell SDK in an Asp.Net Core application, PSRemoting is broken because of the BinaryFormatter long-term obsoletion plan.

To re-enable BinaryFormatter to let PSRemoting works, you have add a property EnableUnsafeBinaryFormatterSerialization set to true in your csproj :

<Project Sdk="Microsoft.NET.Sdk.Web">
	<PropertyGroup>
		<TargetFramework>net5.0</TargetFramework>
		<EnableUnsafeBinaryFormatterSerialization>true</EnableUnsafeBinaryFormatterSerialization>
	</PropertyGroup>
	<ItemGroup>
		<PackageReference Include="Microsoft.PowerShell.SDK" Version="X.X.X" />
	</ItemGroup>
</Project>

[fMichaleczek]

@sdwheeler I'm not an english native, so it's better if I don't write the documentation 😅. It's my first issue in this repo, let's me know if you need more informations.

[SteveL-MSFT]

Our plan is to remove dependency on BinaryFormatter in 7.2 (.NET 6) timeframe. So this only applies to 7.1 which is only supported for a year. The existence of this issue might be sufficient?

[fMichaleczek]

@SteveL-MSFT yes, the error message is clear, the issue is referenced on github. But we can also try set EnableUnsafeBinaryFormatterSerialization to true in the SMA/PowerShell.SDK 7.1.1+ and see if it works in Asp.Net