There are already some issues regarding .net core support: #9 #33
Instead of activly building a test runner with .net core support and supporting the mstest/xunit/nunit core versions, it would be a great idea to split the functionality of axocover into two parts
part one: test/cover run with generation of a trx and opencover.xml file
part two: reading of the trx/opencover.xml files to update the ui.
So for dotnet core projects you could just invoke dotnet test with a string for additional arguments the user woud provide and watch for the trx/coverage.xml files to update.
This way I could write
dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=opencove --logger "trx;LogFileName=testrun.trx"
There are already some issues regarding .net core support: #9 #33
Instead of activly building a test runner with .net core support and supporting the mstest/xunit/nunit core versions, it would be a great idea to split the functionality of axocover into two parts
So for dotnet core projects you could just invoke
dotnet testwith a string for additional arguments the user woud provide and watch for the trx/coverage.xml files to update.This way I could write
and still have coverage markers.