Bug 29948 - Max Linq returning -79228162514264337593543950334
Summary: Max Linq returning -79228162514264337593543950334
Status: RESOLVED DUPLICATE of bug 29570
Alias: None
Product: Android
Classification: Xamarin
Component: BCL Class Libraries ()
Version: 5.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jonathan Pryor
URL:
Depends on:
Blocks:
 
Reported: 2015-05-11 13:49 UTC by jonathan_chapman
Modified: 2015-05-11 14:26 UTC (History)
1 user (show)

Tags:
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:
Status:
RESOLVED DUPLICATE of bug 29570

Description jonathan_chapman 2015-05-11 13:49:08 UTC
I have an observablecollection that I'm applying a Max such as:

collection.Max(x => x.value).

There is only one object in the collection that has a decimal property with a value of 1, so this should return 1.  However, it is returning -79228162514264337593543950334.

This code has worked for a long time but I'm not sure what version it stopped working in because it's been a while since this has been tested.  I'm on version 5.1.1.3 Xamarin Android.
Comment 1 Jonathan Pryor 2015-05-11 14:08:08 UTC
I suspect that this is a DUPE of Bug #29570. We need to investigate.
Comment 2 Jonathan Pryor 2015-05-11 14:26:33 UTC
Confirmed to be a duplicate.

*** This bug has been marked as a duplicate of bug 29570 ***