Does running .Net coverage affect the binaries produced?
Does enabling .Net coverage (for example with dotCover) for a build have an effect on the binaries produced? I'm worried that enabling coverage would add some extra lines (instrumentation) to the code to be able to tell which lines were run which would then cause issues with performance if the binaries produced by the build would be used in production.
Should I make a separate build task for running the code coverage tool to avoid that?
Please sign in to leave a comment.
Hi,
no, binaries are unaffected. In fact, you can create a separate task to build, and another one to test and run the coverage, and the artifacts should be the exact same before and after.