We use this workaround in the acceptance tests to avoid the issue described here: https://docs.microsoft.com/en-us/dotnet/framework/migration-guide/mitigation-deserialization-of-objects-across-app-domains
the workaround is wrapped in #if NET452 but this bug affects all .net framework versions (tested against 4.6.2 and 4.7). Since we ship this code as source files, this workaround doesn't work in case downstreams target some other framework than net452.
cc @SimonCropp
Give our current expected framework targets, the simplest way to handle this would be to change it to #if !NETCOREAPP2_0.
Added to the beta10 milestone
@bording was thinking about this as well. See #5041
Most helpful comment
Give our current expected framework targets, the simplest way to handle this would be to change it to
#if !NETCOREAPP2_0.