Skip to content
This repository has been archived by the owner on Nov 15, 2021. It is now read-only.

DNX Support

Jump to bottom
Neil Cross edited this page Apr 20, 2016 · 4 revisions

DNX is the latest (at the time of writing) way of doing ASP.NET development and there are some gotchas that users of OpenCover have come across when in this environment.

The trick (user supplied) is to use the --lib argument of dnx.exe e.g.

OpenCover.Console.exe -target:"C:\<path-to-dnx>\dnx-clr-win-x86.1.0.0-beta6\bin\dnx.exe" 
    "-targetargs:--lib c:\projects\<path-to-site>\website\bin\debug\dnx451 --lib c:\projects\<path-to-site>\common\bin\debug\dnx451 -p c:\projects\<path-to-tests>\test\Website.Tests test" 
    -output:coverage.xml 
    -filter:+[Website]*

In Continuous Integration environments (like AppVeyor), it might be necessary to run a dnu build before being able to use the generated artifacts. This is especially true when working with DNX class libraries which have no entry point by themselves.

How to use OpenCover - Usage Addressing performance problems with OpenCover

Clone this wiki locally