Closed ViktorHofer closed 10 months ago
That's because 2.5.3 of the VS adapter was released with 2.5.2 of the core framework.
Why does it matter?
Are you coding against runner utility?
Yikes, I should have come up with a repro first... Let me get back to you.
Going to close this as it's not us. I've added comments to https://github.com/dotnet/runtime/issues/94183 and happy to help with any followup necessary there.
xunit.runner.visualstudio.testadapter from
xunit.runner.visualstudio/2.5.3
references xunit/2.5.2 assemblies:You can see that the assembly metadata points to
xunit.runner.utility.net452, Version=2.5.2.0
.When using
xunit/2.5.3
in combination withxunit.runner.visualstudio/2.5.3
, the assembly version ofxunit.runner.utility.net452
in the output directory is2.5.3.0
. This leads to the following failure when invokingdotnet test -f net462 --diag:log.txt
on a .NET Framework test app:The version is hardcoded to 2.5.2 here: https://github.com/xunit/visualstudio.xunit/blob/097b60584fb932d3dcff297de827c543c879c7f4/Versions.props#L13
cc @bradwilson