Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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
GitHub or Developer Community 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.
Created attachment 1984 [details]
Test case which demonstrates inconsistency between Mono and .NET
The order of arguments in IComparer.Compare() in MONO is the inverse of the order of arguments in .NET.
I have attached a test case which demonstrates the issue. It produces the correct result using Microsoft .NET, but an error using MONO.
Running the same test case code, the result on MS .NET is:
Correct result (.NET): 1-3 is in range 0-9
whereas on MONO we have:
ERROR (Mono): The given input was not found in any ranges!
I forgot to say the obvious. I suspect this is a problem in BinarySearch() which passes the arguments in the wrong order.
Fixed in master
Do we need to put this on 2-10 and mobile-master?
No, it's a breaking change which may require user code changes