Open antibarbie opened 3 years ago
After reviewing the code... The culprit could be a project referenced by the wixproj. Or maybe the code is a bit too sensitive.. (This bug could be related to issue https://github.com/wixtoolset/issues/issues/2261). Any suggestion to seek the guilty package among hundreds of packages?
if (projectCfg2 != null)
{
hr = projectCfg2.get_DisplayName(out configuration);
if (hr != 0)
{
Marshal.ThrowExceptionForHR(hr);
}
}
First I was unsure if the bug should be reported to WixToolset or Nunit ; bug the stack trace seems to point to WixToolset.
v3.11.3.4516
Which version of Visual Studio are you building with (if any)?
Microsoft Visual Studio Enterprise 2019 - Version 16.8.4
Which version of the WiX Toolset Visual Studio Extension are you building with (if any)?
1.0.0.4
4.7.2 / .Netstandard2.0 / .Netcore2.1
I am trying to run tests with NUnit and NUnit3TestAdapter versions : NUnit Adapter 3.13.0.0 / NUnit 3.12.0
The Test output in Visual Studio show "ArgumentException" stack traces - Code coverage is completely broken, and test discovery also seems to fail somewhat (maybe that's not an issue if it fails when discovering test in a wixproj).
When unloading .wixproj, code coverage functions properly. With the .Wixproj loaded, code coverage is completely broken.
A short repro: Create a .SLN with a nunit test project and a .vixproj project - use code coverage on the nunit project
ps: I really don't know why should MS-Visual should invoke msbuild on the wixproj when launching code coverage, maybe I can help debugging this extension & send a pull request to make the code more resilient.