Daniel Paz

@tonerdo I'll try to explain better: ```ProjectName.Api``` references ```ProjectName.Application``` and ```ProjectName.Data``` ```ProjectName.Application``` references ```ProjectName.Data``` ```ProjectName.Data``` doesn't reference any of the other two projects I named my projects ```ProjectName.X.Tests``` where X...

In when trying to solve this (pr #225) i found a comment in the code that called my attention In ```Coverage.cs``` line 169 : ``` // File not instrumented, or...

@tonerdo have you had the chance to take a second look at this? Hope it's clear now

@tonerdo I cannot exclude the assembly since it's being used by the classes at my other project . If you ment by command line param, again i can't since i...

@tonerdo you mean the /p:Exclude param then. I have to specify what to exclude and i cannot make a generic test run for all my projects if I do, which...

@tonerdo One option could be adding a command line option param to exclude non used assemblies, if you really want to keep current behaviour as default. Wouldn't mind modifying my...

@tonerdo i updated my pr to add this as an option so default behaviour remains the same and fixes the issues for those who need to exclude non used files...

@vlef i already gave up and forked away. If you use current coverlet, even more things that I don't care about (and maybe you don't either) gets into the report....

Yep. I first wanted to exclude them by default. Then came with this option variable to keep the original behavior for whoever uses it. But no luck it seems 😢

@vlef if you plan to fork, you can copy the code from my original pr (so not the last commit but the first one). That will instrument only the dlls...