Bug 5168 - watches showing "Method `.ctor' not found in type `Int64'." for some enums values
Summary: watches showing "Method `.ctor' not found in type `Int64'." for some enums va...
Status: RESOLVED DUPLICATE of bug 4931
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: 3.0.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
URL:
Depends on:
Blocks:
 
Reported: 2012-05-18 10:23 UTC by Sebastien Pouliot
Modified: 2012-05-18 16:15 UTC (History)
1 user (show)

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


Attachments
screenshot (24.51 KB, image/png)
2012-05-18 10:23 UTC, Sebastien Pouliot
Details


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 4931

Description Sebastien Pouliot 2012-05-18 10:23:56 UTC
Created attachment 1916 [details]
screenshot

Some enum values cannot be shown properly, while others are fine. 

Evaluation of the same value works fine.

Never seen that one prior to MD 3.0
Comment 1 Jeffrey Stedfast 2012-05-18 12:05:43 UTC

*** This bug has been marked as a duplicate of bug 4931 ***
Comment 2 Jeffrey Stedfast 2012-05-18 16:15:19 UTC
n/m, I actually just hit this myself... so not fixed after all :(