Marco Rossignoli

@adamsitnik ask to me to follow up here after https://github.com/dotnet/performance/pull/314#pullrequestreview-206180237 I don't know if new comparer tool will be the same of `BenchmarkDotNet.Tool` but as I said could be useful:...

Yep coverlet needs PDB metadata to instrument and calculate the report. I'll review the PR thanks

There's no ETA yet, we don't have strict schedule, for now you can give it a try using the dogfood and let us now if it's working as expected https://github.com/coverlet-coverage/coverlet#Consume-nightly-build

Thanks for reporting this

Thanks for reporting this. @matteoerigozzi, regression?

Hi all here, at the moment coverlet try to follow the chain of caller(parent classes) in case `[ExludeFromCodeCoverage] ` and also in my local test I'm not able to repro,...

Hi @jsiegmund, first of all you're mixing the configuration for coverlet and MS CodeCoverage parameters, coverlet supports only these https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/VSTestIntegration.md#advanced-options-supported-via-runsettings can you try with: ``` dotnet vstest C:\project\bin\Debug\netcoreapp3.0\publish\testdll.dll --collect:"XPlat Code...

@SeijiSuenaga I think that your scenario is different, the issue inside a docker is related to the fact that coverlet excludes dll if it's not able to locate the sources...

@olga-shtykova if you're out of a docker maybe you should move if possible to the collector integration, msbuild and .NET tools suffer sometimes of a defect related to test platform...

You should try to use the datacollector integration https://github.com/coverlet-coverage/coverlet/blob/master/Documentation/VSTestIntegration.md also inside the docker msbuild integration suffers of the issue described in the known issue doc.