Peter Liljenberg

Do you copy the source code into the docker container in addition to the binaries? Coverlet skips projects with PDBs but no local source files as a heuristic to filter...

It may also be an issue that the path name of the directory containing the code in the docker image is different to the path name outside it, which means...

I don't think you need anything but the `bin` directories of the test projects, but you may be hit by what #1164 describes where the source code must be available...

You can solve this now by configuring Coverlet to output e.g. cobertura or opencover files instead of it's own format, and then use https://github.com/danielpalme/ReportGenerator to merge them into a single...

If 100% code coverage is important to the code in question, a workaround is to move the logic that should be tested into a separate method and tag the entry...

An easier thing to implement is to provide a couple of static wrapper methods that this kind of code can use, and then just check for the top-level usage of...

@SiwinskiK coverlet packages should only be referenced by unit test projects, which generally ought not to be run in IIS, at least not in production. Given that, is this vulnerability...

If possible I'd recommend running a pure unit test run without code coverage enabled and then a second run that collects code coverage. That way any issues that code coverage...

It sounds good, I think. An extension of that thought: would it be possible to _always_ run the coverage test from a new folder containing instrumented DLLs (and all the...

Before going down the shared memory road have a look at this comment from the last time it was tried to see if it can be done in a way...