Brad Wilson

If this can be done without breaking xUnit.net v3 ~(especially the `microsoft-testing-platform` branch)~, then I would be willing to entertain a PR to do this. _**Edit:** The `microsoft-testing-platform` branch has...

I would also be interested to know what the adoption blockers are for users who cannot use v3.

Most of the breaking changes should be here: https://xunit.net/docs/getting-started/v3/migration And there's also a What's New page that can be helpful for people moving: https://xunit.net/docs/getting-started/v3/whats-new

> As you see, the PR is MASSIVE Obviously it's up to you to decide how to achieve your technical goals, but trying to mix v2 and v3 support into...

> Can I have better understanding of the concerns? If you're planning to use the VSTest adapter, then it will insist on making changes that are not compatible to v3,...

> To make sure I'm following, are you referring to runsettings and VSTest filter? No, we support those today. Last I looked, the VSTest => MTP adapter required injection of...

We don't do anything with this setting (I've never even heard of it), so my guess is this is probably a question for the VSTest team rather than us.

I don't believe it has ever been our responsibility to read and respect that value. The logger in VSTest has nothing to do with us.

@zachng1 Sure!

FWIW, I just added support for this in xUnit.net after going many years without realizing that VSTest overrides the `DefaultTestListener`. 😁 https://github.com/xunit/xunit/issues/3220 https://github.com/xunit/xunit/commit/4c931758375b071414f70423e810b8a83c2e3221