You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We use MSBuild.exe and vstest.console.exe rather than the dotnet cli due to incompatibility with mixed C++ / C# projects. The trouble is, both suggested uses of coverlet.collector require either dotnet test or dotnet publish. Ideally coverlet.collector should have a method of triggering the deployment that isn't via the dotnet cli tool unless there is some inherent incompatibility with mixed C++ / C# projects.
The text was updated successfully, but these errors were encountered:
Hey I've finished deep diving into getting this working now, dotnet vstest has the same problem as vstest.console.exe where we really need to run a dotnet publish first. The solution to my problem was realizing that you can run MSBuild.exe with the arguments /p:DebugType=portable /p:PublishProfile=<profile name> /t:Publish in order to get an output that includes the required coverlet files. This really isn't a problem with coverlet but perhaps is an opportunity to improve documentation.
We use
MSBuild.exe
andvstest.console.exe
rather than thedotnet
cli due to incompatibility with mixed C++ / C# projects. The trouble is, both suggested uses ofcoverlet.collector
require eitherdotnet test
ordotnet publish
. Ideally coverlet.collector should have a method of triggering the deployment that isn't via thedotnet
cli tool unless there is some inherent incompatibility with mixed C++ / C# projects.The text was updated successfully, but these errors were encountered: