Brad Wilson

Writing tests in netstandard is not supported. https://xunit.net/docs/why-no-netstandard

The minimum supported version of .NET Framework is 4.5.2 (for xUnit.net v2). If your tests must be written in .NET 4.0 then you can use xUnit.net 1.x, but it is...

> and even deadlocks You can deadlock the max concurrency context, which you already have a way to opt out of. Looking at the code, I cannot see how you...

Without a repro it's hard to know exactly what's going on here, but if you're using .NET Framework (as opposed to .NET Core/.NET 5+), then my suspicion is that it...

Given dependency resolution order (especially in .NET Core), it wasn't possible for that class to exist in xunit.runner.utility.dll, because it is required to successfully locate and load xunit.runner.utility.dll. So it...

>So, what's a third party runner to do? We can't provide you with a binary that works, so you'll have to take a copy of the source for yourself, I'm...

...and that .NET Core code is the code you can't really trust to always do the right thing, I'm afraid. It's why we killed `dotnet xunit` and the CoreCLR `xunit.console.dll`.

I've added my thoughts in https://github.com/dotnet/csharplang/issues/287#issuecomment-353248246 already, which I'll reproduce here: ----- > I don't think breaking unit tests is as important as breaking non-test code In the case of...

This feature has landed in the C# 10 compiler in .NET 6.0 SDK. I'm still doubtful about the usage with the assertion library here. Let's talk about the two specific...

The discussion around `[BinaryCompatOnly]` certainly does solve my usability issues, and I think would prevent me from needing to ship two separate versions of my assembly... except, I'm guessing that...