Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
I have already...
My issue is related to (check only those which apply):
I have been using OpenCover for about a year now with no issues. I am running it via the following powershell script:
When running it locally against my code, I get the expected output:
However, when running the exact same script in Azure DevOps (which is using the same laptop/user as the build agent) I get the error where no coverage results are available:
Steps to reproduce the problem:
There's a similar Azure DevOps issue mentioned in this comment; the work-round in that case was to use
As a guess, I wonder whether the Azure process is running with sufficient privilege to register a COM object, even as user, or whether it's too heavily sandboxed for that.
@SteveGilham Holy cow that worked! After months of using -register:user without fail, switching to -register:Path32 was all that was needed. Thank you for your help!