Today, we're shipping xUnit.net 2.4.1; this includes RTM builds of the core framework and the Visual Studio runner. This build is primarily a maintenance release for 2.4, and represents what we hope is the final build in the 2.x lifetime.
It's been 3 months since the release of 2.4 RTM. The small number of issues fixed here are due to the relative stability of the codebase especially as we turn our focus to working on 3.0.
xUnit.net version 1.x was really about perfecting the experience of writing unit tests for the desktop CLR. Version 2.x expanded support for many platforms, including .NET Core, Xamarin (iOS and Android), UWP, and others along the way. Now that we've reached the edges with the current platforms, it's time for us to focus on 3.0. The 3.0 issues list is where you can track our work towards the next major version. Please feel free to open any new issue for any bug or missing feature that you'd like considered for the 3.0 time frame.
As always, we'd like to thank all the users who contributed to the success of xUnit.net through usage, feedback, and code contributions. We had too many contributors this time around to thank individually, so know that every bug reported, every line of code PR'd, every conversation contributed to on Slack, were all appreciated!
These release notes reflect the entirety of the changes between 2.4 and 2.4.1.
IAsyncLifetime) runs to
completion before synchronous disposal (via
netstandard2.0 libraries. Developers who were using desktop CLR
versions older than 4.7.2 could encounter assembly loading issues. We rolled
this change back, which should resolve the issue for those users. For more
information on this problems caused by the original change, see this Github issue.
-nocolor was not
honored (when trying to get any reports other than XML v2 from the .NET Core