OpenCover crash when reference assembly finish by Fakes

[calimero100582]

Please provide the following information when submitting an issue.

Where appropriate replace the [ ] with a [X]

My Framework

• .NET 2
• .NET 3.5
• .NET 4
• .NET 4.5
• .NET 4.6
• .NET 4.6.1
• .NET 4.6.2
• .NET 4.7
• .NET 4.7.1
• .NET 4.7.2
• .NET Core 1.0.0
• .NET Core 2.0.0
• Something else

My Environment

• Windows 7 or below (not truly supported due to EOL)
• Windows 8
• Windows 8.1
• Windows 10
• Windows 10 IoT Core
• Windows Server 2012
• Windows Server 2012 R2
• Windows Server 2016

I have already...

• repeated the problem using the latest stable release of OpenCover.
• reviewed the usage guide and usage document.
• have looked at the opencover output xml file in an attempt to resolve the issue.
• reviewed the current issues to check that the issue isn't already known.

My issue is related to (check only those which apply):

• no coverage being recorded
• 32 or 64 bit support
• feature request

Expected Behavior

Code Coverage returned as usual

Actual Behavior

No Code Coverage returned

Steps to reproduce the problem:

Create a new test project
Create a new class library with any name finishing by ".Fakes"
Run Tests with OpenCover, return a CodeCoverage
Add reference from Test project to class library
Run Tests with OpenCover, no CodeCoverage returned

In the screenshot below Class1.cs and UnitTest1.cs contain only empty class, and empty test method

• reviewed the usage guide and usage document again because we know you probably didn't do it the first time.
• sample code or link to repository/gist is available (support is much faster this way)

[sawilde]

Both Fakes and OpenCover use the profiling API and as you can imagine things don't always play well.

OpenCover does attempt to see if the Fakes profiler is running and attempt to intercept but it seems to be a moving target for every release of the test/fakes runner.

I'll see if I can get it working with VS2017 but I can't guarantee anything...

[barisgul]

Hi @sawilde ,
Is there any progress about this problem? we also having same issue. The issue is in progress since Mar 18, 2019 as i seen.