Bug 2163 - Evaluation of Nullable<> types in watch fails with TypeLoadException
Summary: Evaluation of Nullable<> types in watch fails with TypeLoadException
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 2.8.2
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2011-11-22 17:04 UTC by Felix Collins
Modified: 2012-05-31 15:01 UTC (History)
2 users (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 FIXED

Description Felix Collins 2011-11-22 17:04:47 UTC
On version 2.8.2 as shipped by Xamarin for MonoDroid, evaluation of Nullable<> types in watch fails with TypeLoadException. Running on windows 7.

1. Create a class with a Nullable<int> property
2. In main of a console app create an instance of the class
3. Break after instance is created and enter a watch of the instance
4. Try to view the value of your Nullable<int> member

The value displays as "Evaluation failed: System.TypeLoadException"
Comment 1 Jeffrey Stedfast 2012-05-31 15:01:54 UTC
I'm pretty sure this was fixed (also not able to reproduce with latest MonoDevelop & Mono 2.10.9)