Bug 5172 - Inspecting nullable properties results incorrect
Summary: Inspecting nullable properties results incorrect
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.2.x
Hardware: PC Windows
: Normal normal
Target Milestone: 4.8 (async)
Assignee: Bugzilla
Depends on:
Reported: 2012-05-18 12:21 UTC by Jonathan Pobst
Modified: 2013-06-28 14:11 UTC (History)
6 users (show)

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

Screenshot (11.41 KB, image/png)
2012-05-18 12:21 UTC, Jonathan Pobst

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 Jonathan Pobst 2012-05-18 12:21:00 UTC
Created attachment 1917 [details]

When inspecting nullable properties on a class, HasValue always returns false.

Tested in WinMD 3.0 / MFA 4.2.1.

See attached screenshot.
Comment 1 Jeffrey Stedfast 2012-05-31 15:26:31 UTC
This was a runtime bug which was fixed a while ago by Zoltan.

M4A probably needs an updated mono
Comment 3 Jonathan Pryor 2013-06-28 14:11:52 UTC
Does this still repro? As per Comment #1, this was fixed in mono, and 4.7.x is now using a very recent mono...