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
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.
The debugger should have special support for Nullable<T>. When displaying a value of type Nullable<T>, it should check the has_value field (it seems a safe assumption that the internals of Nullable<T> will never change, no point in adding property evaluation overhead). If this value is false, the debugger should just render "null". If it's true, it should fetch the object from the value field and render that object directly in-place. The actual Nullable<T> object should not be displayed at all.
This will save a level of drilldown to get the value from nullables, and avoid exceptions when evaluating the Value if it's null.
Jeff, can this get higher priority. MT is full of nullable properties and this is annoying.
fixed in git master