Bug 14495 - NUnit library regressed to 2.4
Summary: NUnit library regressed to 2.4
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: NUnit ()
Version: 4.1.10
Hardware: Macintosh Mac OS
: Normal normal
Target Milestone: master
Assignee: Mike Krüger
Depends on:
Reported: 2013-09-06 15:23 UTC by John Lyon-Smith
Modified: 2015-11-19 04:50 UTC (History)
2 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community or GitHub with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description John Lyon-Smith 2013-09-06 15:23:58 UTC
Description of Problem:
It seems that the version of NUnit included with Xamarin Studio is now pre-2.5.

Steps to reproduce the problem:
1. Create a unit test project
2. Add a test with a call to Assert.NotNull(null)
3. Try and compile.

Actual Results:
Get an error stating that the method NotNull is not found

Expected Results:
NotNull should be present on the Assert class (as it was prior to this release)

How often does this happen? 

Additional Information:
Comment 1 Mike Krüger 2013-10-14 04:36:47 UTC
Was caused by a change in the build engine.
As workaround open the project options & turn of 'use msbuild engine'.
Comment 2 Mike Krüger 2015-11-19 04:50:24 UTC
Was fixed in the mean time - closing.

(Note: We're going to upgrade to 3.0 soon after the 6.0 release)