If I install OpenCover into a solution via NuGet, I get the expected files under, e.g., a packages\OpenCover.4.5.1604 folder. However, OpenCover's profilers require COM registration in order to function properly. I recognize that it's possible to use a -register
command to do a run-time registration of these, but on a machine with multiple solutions, which may potentially have different versions of OpenCover installed (and which could be executing them simultaneously -- e.g., a build server), this seems problematic.
This SO answer from the author himself indicates that calling regsvr32
separately to register the profilers once would be preferable on a build server, and that makes sense. But in the situation where OpenCover has been pulled down via NuGet (into the solution), is there a proper build server solution? Or is NuGet simply a convenient way to get the files, but they should really be copied to a centralized location and then registered, rather than attempting to be run from a solution-specific version?