Release Notes: October 27, 2017

Hello, v2 2.3.1!

Today, we're shipping xUnit.net 2.3.1. This is primarily a bug fix release. The complete list of issues fixed since 2.3 is listed below.

Removed external dependencies. This primarily caused issues with developers who wanted to use a newer version of JSON.NET than we were linked against (9.0.1), but also affected uses of Microsoft.DotNet.InternalAbstractions and Microsoft.Extensions.DependencyModel.

Optimized assembly resolution lookup performance.
Made the -quiet switch cause less output from dotnet xunit itself, as well as switching the default MSBuild verbosity to quiet.
When exiting with Ctrl+C, the standard Windows exit code (0xC000013A, or -1073741510) is now correctly used. In addition, Ctrl+C handling has been improved (for example, when attempting to stop during a build, the runner would previously move onto the next target framework instead of immediately stopping).
BUG: Fixed an issue where hitting Ctrl+C did not correctly terminate all the child processes created by dotnet xunit.
BUG: Assembly resolution sometimes failed on case-sensitive file systems (this primarily affected Linux users, as Windows and OS X by default use case-preserving but case-insensitive file systems).
BUG: Unmanaged library lookup would sometimes fail because of names which didn't match the filename (for example, asking for 'foo' but the library is really 'libfoo'). This primarily affected Linux and OS X users where dynamic libraries tend to have prefixes like 'lib'.

When exiting with Ctrl+C, the standard Windows exit code (0xC000013A, or -1073741510) is now correctly used.
BUG: Fixed an issue where the XML results file was being over-written without erasing the old contents, the end result of which could be corrupted XML files.

BUG: Fixed an issue where MSBuild runner reporters were not working. This was most obviously affecting TeamCity and AppVeyor users who lost their test reporting.
BUG: The XML results output file was being left open longer than intended. Now it should be closed by the time the <xunit> task has completed.
BUG: All reports other than XML v2 (for example, HTML and NUnit) were failing to output correctly, instead causing a null reference exception.

For information on using xUnit.net from within Visual Studio, see Running tests with Visual Studio in the Getting Started documentation.

BUG: Fixed issues with the performance-optimized serialization that were causing [Fact] tests to be broken with Live Unit Testing.
BUG: Fixed an issue where test classes with mixed facts and theories and class/collection fixtures ended up with two fixtures being created (one for the facts and one for the theories).
BUG: Fixed an issue where sometimes source file mappings were broken, especially with projects whose name started with 'n'. (Yes, really.)

BUG: Fixed an issue with the JSON reporter which caused floating point numbers to use the current computer's locale to format numbers, instead of the invariant locale. This caused invalid JSON to be generated on systems which use non-period decimal separators.