Tests fail if assembly is strong named

I’m trying to use Coverlet against an assembly that is strong named. When running those tests on the .NET 4.6.1 target, I get many errors similar to this:

Failed   Tests.MinMax.Min_AsyncSelector_Int32_4
Error Message:
 System.TypeInitializationException : The type initializer for 'Tests.AsyncEnumerableTests' threw an exception.
---- System.IO.FileLoadException : Could not load file or assembly 'System.Linq.Async, Version=4.0.0.0, Culture=neutral, PublicKeyToken=94bc3704cddfc263' or one of its dependencies. Strong name signature could not be verified.  The assembly may have been tampered with, or it was delay signed but not fully signed with the correct private key. (Exception from HRESULT: 0x80131045)
Stack Trace:
   at Tests.AsyncEnumerableTests..ctor()
   at Tests.MinMax..ctor()
----- Inner Stack Trace -----
   at Tests.AsyncEnumerableTests..cctor()

Is there a way to make this work?

[MarcoRossignoli]

Thank’s for your opinion, it’s very appreciated really. I’m reading/listening on media the trends rumors and I don’t have a strong opinion today. We have a pair of issue on netfx and I’m a “bit” alone at the moment, so my idea is to work more on “default/expected coverlet enviroment”, it’s the default .net core cross code coverage tool AFAIK and it’s the build-in choice for dotnet test so I’m putting more effort on better vstest integration and support better msbuild features(msbuild suffer of very time spending investigation issue https://github.com/tonerdo/coverlet/blob/master/Documentation/KnowIssues.md#1-vstest-stops-process-execution-earlydotnet-test). But as maintainer I don’t forget anybody and I try to track and spend my time to improve this tool on every aspect and better I can, so sorry for these defects 😞 You can read discussion here and add your opinion https://github.com/tonerdo/coverlet/issues/683 https://github.com/tonerdo/coverlet/pull/704

[MarcoRossignoli]

@tonerdo maybe we should document?