Release Notes: March 9, 2015

Support for ASP.NET 5 has been removed from this build in preparation for RTM. Once 2.0 goes RTM, a new beta build (2.1 Beta 1) will be released which restores ASP.NET 5 support. If you're using ASP.NET 5, you can continue to use this documentation (and continue to use rc3 in your version numbers).

xUnit.net v2 2.0 RC 4

Core framework

The old NuGet package xunit.runners was split into two separate packages: xunit.runner.console and xunit.runner.msbuild. The latter automatically makes the <xunit> task available from within the project file (.csproj, .vbproj, etc.). With this new behavior, you can easily add targets which invoke the MSBuild runner, and you won't need to update your projects by hand when upgrading to a new version of xUnit.net.
BUG: Fixed a serialization issue related to open generic types (f.e., IEnumerable<>).
BUG: Resolved an issue where enum types were not always able to be deserialized, but which wasn't discovered until the deserialization was attempted. Now, enums from GAC assemblies will just refuse serialization; the end result of this is that theories which use GAC-based enum values (like those from the CLR itself) will not be individually runnable from within Visual Studio (there will be a single test case for all theory data members).

Extensibility

Improved diagnostics around incorrectly configured and misbehaving test collection orderers and test case orders.
A -serialize switch was added to the console runner to force it to serialize and de-serialize all discovered test cases. This should aid developers who need to debug through their test case serialization code, without forcing them to use the MSBuild or Visual Studio runners.
Developers who write extensibility libraries that are linked against the execution library can now decorate their assemblies and extensibility points to indicate that they support multiple platforms. This is useful for any type which is serialized (such as test cases) or for any time you need to provide a type name and assembly name to an extensibility registration attribute.

There are three steps that the developer should do to opt into this new behavior:
1. Name your assemblies with the correct platform suffixes (for example, MyAssembly.desktop.dll). The currently supported suffixes are:
  - desktop (for desktop CLR)
  - iOS-Universal (for Xamarin iOS Universal)
  - MonoAndroid (for Xamarin Mono Android)
  - MonoTouch (for Xamarin Mono Touch)
  - universal (for universal Windows 8.1/Windows Phone 8.1)
  - win8 (for Modern Windows 8)
  - wp8 (for Windows Phone 8 Silverlight)
  Note that on some platforms, the file system may be case sensitive, so please use the exact casing shown here.
2. Decorate your assemblies with an attribute which lets the system know that it is a platform specific assembly:
  [assembly: PlatformSpecificAssembly] (example).
3. Decorate your extensibility point registrations with an assembly name that substitutes {Platform} for the platform part of the assembly name (example).
Note: Developers who are writing extensions but only intend to support the desktop platform do not need to do any of these steps.
The MemberDataAttribute class implementation was split into a base class (MemberDataAttributeBase) which better facilitates behavior reuse.

Console Runner

BUG: Fixed an issue with NUnit output and multiple test assemblies.

TestDriven.NET Runner

The progress bar during runs should be more useful now. :)

Mono

A new solution file (xunit.xbuild.sln) has been added to facilitate Mono builds on Linux and OS X using XBuild. A build shell script will be added before RTM to make this process easier.

Visual Studio Runner 2.0 RC 4

For information on using xUnit.net from within Visual Studio, see Running xUnit.net tests in Visual Studio.

Note: This release supports all released versions of xUnit.net v1, as well as v2 2.0 RC 4 or later. It does not support any earlier versions of xUnit.net v2.

There were no issues fixed for this release.