Not getting Code Coverage - Warning HRESULT E_FAIL

Completed

I'm working with the trial of Resharper ultimate for assessment.

Currently trying to get Code Coverage results but after running coverage is always at 0% throughout the codebase. l am however getting the following warning when running 'Cover Unit Tests' and do not get it when using the standard 'Run Unit Tests',

"WARN Coverage analysis: Profiler message: Error HRESULT E_FAIL has been returned from a call to a COM component API was requested, but wasn't called (C:\Program Files\dotnet\dotnet.exe [pid=18016])"

Few things to check first really:

- dotcover works with Visual Studio Community edition?

- dotcover works with .Net core?

- dotcover works with xUnit?

Versions:

JetBrains ReSharper Ultimate 2019.1.2 Build 191.0.20190603.142841
dotCover 2019.1.20190603.145814
dotTrace 2019.1.20190603.145722
ReSharper 2019.1.20190603.145621

Visual Studio Community 2019 version 16.1.2.

8 comments
Comment actions Permalink

Hello,

Yes, dotCover works with Visual Studio Community edition, .Net Core, and xUnit.

Could you please say which version of .Net Core you are using? Currently, we have a problem with supporting .Net Core 3.0 preview 4 and greater: https://youtrack.jetbrains.com/issue/DCVR-9731

1
Comment actions Permalink

Hi Ekaterina,

Thanks for getting back to me.

I was using .Net Core 3.0 preview 4 and rolled back to 2.2 and I'm getting coverage results now.

Thanks for your help.

0
Comment actions Permalink

Hi,

The fix is available in ReSharper/Rider 2019.2 EAP2 build. It should work fine with .Net Core 3.0 Preview 6.

0
Comment actions Permalink

Hi Fedor Buyvol-Kot,

Today I upgraded my projects to the new .Net Core 3.1 version which was released yesterday.

But I have similar issues as Aazarus

2019.12.04 15:15:15.709 WARN Coverage analysis: Profiler message: API was requested, but wasn't called (C:\Program Files\dotnet\dotnet.exe [pid=9428])
2019.12.04 15:15:16.568 WARN Coverage analysis: Profiler message: API was requested, but wasn't called (C:\Program Files\dotnet\dotnet.exe [pid=10744])
2019.12.04 15:16:15.103 WARN Coverage analysis: Profiler message: API was requested, but wasn't called (C:\Program Files\dotnet\dotnet.exe [pid=19540])

 

 

0
Comment actions Permalink

Здравствуйте Федор,

We have exactly the same problem after updating to .Net Core 3.1 and VS Professional 16.4

2019.12.05 10:30:46.626 WARN Coverage analysis: Profiler message: API was requested, but wasn't called (C:\Program Files\dotnet\dotnet.exe [pid=14200])
2019.12.05 10:30:52.154 WARN Coverage analysis: Profiler message: API was requested, but wasn't called (C:\Program Files\dotnet\dotnet.exe [pid=22684])
2019.12.05 10:30:57.342 WARN Coverage analysis: Profiler message: API was requested, but wasn't called (C:\Program Files\dotnet\dotnet.exe [pid=21040])

 

0
Comment actions Permalink

Hello,

I'm relieved that I'm not the only one with issue... Same problem here :

2019.12.06 10:12:32.609 WARN Coverage analysis: Profiler message: API was requested, but wasn't called (C:\Program Files\dotnet\dotnet.exe [pid=5796])

It appeared after an upgrade of my projects to .net 3.1

 

0
Comment actions Permalink

Hello,

You have faced with a known issue: DCVR-9883. Per Fedor's comment: our profiler from R# 2019.2.3 can't work with .Net Core 3.1, because of changes made in .Net Core after R# 2019.2.3 was released. You could either re-install .Net Core 3.0 and use R# 2019.2.3 or wait a little bit for R# 2019.3 release, in it our profiler works fine with .Net Core 3.1. Please accept our apologies for the inconvenience made.

0
Comment actions Permalink

Спасибо Оля!

When 2019.3 is going to be released to the public?

Hope it will be before 2020...

0

Please sign in to leave a comment.