.net core support

Question

.net core support

sawilde opened this issue 9 years ago · 15 comments

https://github.com/dotnet/corefx/issues/8880

@sawilde, does OpenCover have a hard dependency on mscorlib.dll being named "mscorlib"? The core library has been renamed for .NET Core from "mscorlib" to "System.Private.Corelib", and I'm wondering if that change explains why OpenCover is reporting 0 hits on everything.

So we need to add hooks for that assembly name in CuckooSupportCompilation.

Answer 1 · 2016-06-06T03:23:16.000Z

They are currently using the -oldstyle switch - which seems to be working for them

Answer 2 · 2017-04-20T17:31:53.000Z

Question on this - is the .NET Core support going to be only Windows, or also support macOS, Linux, etc.? Thanks!

Answer 3 · 2017-04-20T21:14:01.000Z

@joemcbride currently it is windows only because we rely on the profiling API which is COM based (an ancient technology in modern IT terms that I cut my teeth on in my youth).

There is this thread on the .net core clr repo regarding the Profiling API that I am keeping my eye on but until they release it xplat (the release keeps shifting) I am unable to do anything with that.

Answer 4 · 2017-04-20T22:03:56.000Z

Drats, well here's to hoping. Thanks!

Answer 5 · 2017-04-29T20:12:14.000Z

an ancient technology in modern IT terms that I cut my teeth on in my youth

@sawilde Stop it, you're making me nostalgic for those days back in Henley-on-Thames 😃

Answer 6 · 2017-12-29T21:38:01.000Z

@sawilde https://github.com/dotnet/coreclr/issues/15136 and https://github.com/noahfalk/coreclr/blob/master/Documentation/project-docs/profiling-api-status.md now list Linux as working, so might you might check that.

Answer 7 · 2018-01-03T04:55:53.000Z

@psibernetic I have been looking at it - the windows one took months of part-time development - so don't expect anything soon - it isn't a simple port.

Answer 8 · 2018-01-27T16:02:04.000Z

Hi there. I'm using an appveyor build of OpenCover with a Mono.Cecil beta that works pretty well for Netcore (C# and F#) with portable debug symbols. I can fully understand though that you prefer to wait for a final release of Mono.Cecil before doing a release for OpenCover again. That said I'm not sure anymore that Mono.Cecil will ever come out of beta. Is there an alternative in that case?

Answer 9 · 2018-03-06T23:51:31.000Z

@jp7677 I don't have one as yet - I've been looking at starting again using the new profiler APIs that come with .net core but I just don't have the time at the moment.

Answer 10 · 2018-03-19T17:57:42.000Z

@sawilde Mono.Cecil 0.10 was just released with support for portable PDB formats. 😄 Do you know if the next release will support only portable PDB files on disk, or also support portable PDBs that are embedded in the binary?

Answer 11 · 2018-03-19T19:08:31.000Z

In the .NET Core repos, we are eager to move to an OpenCover that supported portable PDB

Answer 12 · 2018-03-21T05:41:03.000Z

YES! I've sort of stopped looking!

@sharwell hopefully both - though I may need to tinker with how I use mono.cecil - got easter break coming up so will hopefully find a few days over that period - pray for rainy weather!

Answer 13 · 2018-04-06T22:55:14.000Z

Any luck over Easter @sawilde ?

Answer 14 · 2021-01-02T00:46:48.000Z

We can handle .net core but the support has been patchy with what looks like the PDBs changing format.

Portable and Embedded works with .net 2.2 using the -oldstyle switch - I suspect this is because the Cuckoos aren't loading

Answer 15 · 2021-01-10T21:43:48.000Z

We get coverage from .net core 2.2 and .net core 3.1 using the -oldstyle switch and .net 5.0 with or without that switch

Try the release candidate 4.7.1137-rc or a later build