Test runner issues with ReSharper/Rider 2020.2 EAP6+

ReSharper/Rider 2020.2 EAP6 introduced a change in the test runner which breaks the tests that use ExecuteTestRun on .NET Core.

The new runner loads the tested assemblies in a separate AssemblyLoadContext (not the default one). The call to Assembly.Load(byte[]) in ExecuteTestRun creates its own AssemblyLoadContext to load the assembly, which means its dependencies are no longer resolved correctly, as they are not loaded in the default context by the new runner version anymore.

Read more details in the issue I reported to JetBrains.

There will be a new emulate dotnet vstest resolve option in EAP8 which should fix this, but it will be disabled by default. I’ll wait for EAP8 to ship and then fix this in Fody so we can get the correct behavior by default.

[SimonCropp]

NET Core target to the FodyHelpers

I think that should be fine.

[ltrzesniewski]

I’d say the main drawbacks are the additional target in FodyHelpers and the slightly increased code complexity.