Skip to content

Set the target for OpenCover #209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
tonyhallett opened this issue Nov 18, 2021 · 2 comments
Closed

Set the target for OpenCover #209

tonyhallett opened this issue Nov 18, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@tonyhallett
Copy link
Collaborator

As per @BOnstwedder request

Last I was wondering if it were possible to set the target for opencover, as it would be nice to set this to our locally installed nunit3console exe

in #136 (comment)

@FortuneN

I was going to add an option for the register argument as there appears to be a requirement for it #167 and #191 (comment).

Apparently below is not sufficient.

project.Is64Bit = container.TargetPlatform.ToString().ToLower().Equals("x64");

• -register[:user] - Use this switch to register and de-register the code coverage profiler. Alternatively use the optional user argument to do per-user registration where the user account does not have administrative permissions. Alternatively use an administrative account to register the profilers using the regsvr32 utility.
If you do not want to use the registry entries, use -register[:Path32] or -register[:Path64]to let OpenCover select the profiler for you. Depending on your choice it selects the /x86/OpenCover.Profiler.dll or /x64/OpenCover.Profiler.dll.
You should also consider using path32 and path64 options when profiling .net core targeted applications and .net 4.8 framework.

How would you like to proceed on the register argument, target ( and target args ) and additional arguments that we do not provide ?

@tonyhallett tonyhallett added the enhancement New feature or request label Nov 18, 2021
@FortuneN
Copy link
Owner

FortuneN commented Nov 21, 2021

The assumption was that we could auto determine what is required.

Since, it seems, we cannot do that in all cases we could allow manual input to override the automatic default.
If we know something new we should continue to improve the automatic default so that manual input is required for a minority of cases.

@tonyhallett
Copy link
Collaborator Author

Available in latest version

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants