Bug 6251 - Properties redeclared with 'new' are not evaluated correctly by the debugger
Summary: Properties redeclared with 'new' are not evaluated correctly by the debugger
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-07-24 09:27 UTC by Alan McGovern
Modified: 2012-07-26 12:07 UTC (History)
2 users (show)

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:

Description Alan McGovern 2012-07-24 09:27:58 UTC
public class BaseClass
    public int Foo {
        get { return 5; }

public class DerivedClass : BaseClass
    public int Foo {
        get { return 10; }

BaseClass o = new DerivedClass ();
Console.WriteLine (o.Foo);

The Console.WriteLine will print '5' but the debugger will display '10'. The debugger should be using the static type (BaseClass), not the runtime type (DerivedClass) when figuring out what method to invoke.
Comment 1 Alan McGovern 2012-07-24 09:28:35 UTC
The immediate window exhibits the same (broken) behaviour.
Comment 2 Alan McGovern 2012-07-24 09:30:21 UTC
That should actually be:

public class DerivedClass : BaseClass
    public new int Foo {
        get { return 10; }

But I don't think the 'new' matters in this scenario.
Comment 3 Jeffrey Stedfast 2012-07-26 12:07:52 UTC
this just happens to have been fixed by the same patch as bug #5895