FluentAssertions 2.0.1

What's new in 2.0.1 * Small bug-fix to better intercept and/or prevent exceptions while scanning for methods annotated with [ValueFormatter] What are the major features * Added support for .NET 4.5, Windows Phone 7.5 and .NET for Windows Store Apps * Added support for MBUnit and the Gallio framework * Added a completely new extensible API for comparing two objects graph for equivalence that will replace the object.ShouldHave() API in the future (issue 11841). What's new for collections * Added (Not)BeInAscendingOrder() and (Not)BeInDescendingOrder() (issue 12103) * Added IntersectWith(otherCollection) and NotIntersectWith(otherCollection) (issue 12248) * ContainInOrder() now has an overload that only takes a params object[] argument to support a more fluent syntax in case you don't specify the reason (issue 12313). * Added ContainSingle(Expression<Func<T, bool=""> predicate>) that asserts there is only a single element in the collection that matches the specified predicate (issue 12313). * Added support for a lambda that is used for checking the equality of two collections (issue 11925). * Fixed a bug that occurs when two collections are compared for equality but the collection contains null (issue 12296) What's new for strings * When strings differ in length, it will report the expected and actual lengths as part of the failure messages (issue 12422) * An ArgumentOutOfRangeException was thrown when asserting a string started with a specific string, but the first string was shorter than the expected string (issue 12293) What's new for numbers * Added support for using Should().Be() on nullable numeric types (issue 11837) * Added BeOneOf() to verify that the value matching one of the provided values (issue 12016). * Added support for (nullable) decimals * BePositive() and BeNegative() now also work for floats and doubles (issue 11946) What's new for dates and times * Added NotBe() * Added BeOneOf() to verify that the value matching one of the provided values (issue 12016). * Added BeCloseTo() to assert that a datetime is within a specified number of milliseconds from another datetime value. Usefull for example when your database truncates datetime values (issue 12070). * If a DateTime value has milliseconds then they will be displayed in an assertion failure message (issue 12072). What's new for comparing object graphs * You can now apply the property equality comparisons to entire collections of objects. It doesn't matter what kind of collections types you use, as long as they contain the same number of objects which properties are the same (issue 11743). * Included the index of the mismatching object when comparing a collection for structural equality * An exception was thrown when comparing the properties of an object, and there were cyclic references. You can now configure if you want this to be ignored. * Added support for comparing references to an interface rather than concrete types (issue 11840). * Write-only properties are ignored (issue 11808) * Fixed a stack overflow exception when formatting an object graph containing static cyclic references. * Fixed an exception that was thrown when formatting an object graph where one of the properties threw an exception. * Added support for comparing two anonymous types using SharedProperties() (issue 11886). * The name of a DateTime property was not included in the error message when AllProperties() failed on that property What's new for types * Added the AllTypes class with a static method From(Assembly assembly) as a wrapper around the Types extension method on Assembly (issue 12186). This allows for a more fluent syntax like AllTypes.From(assembly).ThatImplement<SomeInterface>().Should().BeDecoratedWith<SomeAttribute>(); * Added support for asserting the properties of an attribute have a specific value (issue 12186). What other improvements are new * Fixed an exception when asserting equality of dictionaries that contain nulls (issue 12004). * The NuGet package will automatically add references to System.Xml and System.Xml.Linq * Implemented ShouldThrow<TException>() for Func<Task>, to support working with async methods (issue 12148) * Improved several error messages in XDocument- and XElementAssertions * All overloads that take a reason have been removed and replaced with optional parameter * Allowed ShouldRaisePropertyChangeFor(null) to verify that the INotifyPropertyChanged was raised for all properties. * The list of ValueFormatters on the Verification class can be changed to insert a custom formatter. * Introduced a mechanism to override the way FA formats objects in failure message by annotating a static method with the [ValueFormatter] attribute (issue 12364). * Introduced a mechanism so that the failure message of custom extensions can specify the {context} tag. * NuGet package is now based on NuGet 2.0. Breaking changes * The FluentAssertions.Assertions namespace no longer exists so that all extension methods are always available through the FluentAssertions namespace. Just use a global search-replace to remove all those usage statements. * Many of the assertion classes have moved into dedicated namespaces. You might have to fix any code that inherits from those classes. * Remove the obsolete Verify() methods from the Verification class