For MSBuild integration multiple output formats does not work
See original GitHub issueMy unit test project contains coverlet.msbuild
package. When I run dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=opencover,lcov
I received
MSBUILD : error MSB1006: Property is not valid.
Switch: lcov
For switch syntax, type "MSBuild -help"
Issue Analytics
- State:
- Created 4 years ago
- Comments:6
Top Results From Across the Web
For MSBuild integration multiple output formats does not work
My unit test project contains coverlet.msbuild package. When I run dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat=opencover ...
Read more >What would be a reason for msbuild yo put out different ...
Hi @hakubex, The output file contain some packages, if it already exists locally, it will not be generated again, please clean the local...
Read more >The SonarScanner for MSBuild integration failed: SonarQube ...
I had this issue with a self-hosted agent pool in Azure DevOps where a single VM would run multiple builds in parallel. There's...
Read more >MSBuild reference for .NET SDK projects
This page is a reference for the MSBuild properties and items that you can use to configure .NET projects. Note. This page is...
Read more >MSBuild No outputs for project [x] were provided, but the ...
I have an InstallShield 2010 project with Visual Studio integration. The installer builds fine within VS IDE, but when I try to build...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ah ok sorry it was on guide try with
PS C:\git\coverlet> dotnet test /p:CollectCoverage=true /p:CoverletOutputFormat="opencover%2clcov"
%2c
is translated to comma.Is already present…but yes a bit cryptic and hidden
To exclude or include multiple assemblies when using Powershell scripts or creating a .yaml file for a VSTS build %2c should be used as a separator. Msbuild will translate this symbol to ,