Bug 12804 - No code completion in Expression Evaluator and Watch Pad
Summary: No code completion in Expression Evaluator and Watch Pad
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: Trunk
Hardware: PC Linux
: Normal normal
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2013-06-21 05:03 UTC by ventsislav mladenov
Modified: 2013-07-25 16:13 UTC (History)
2 users (show)

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

Test program source (496 bytes, text/x-csharp)
2013-06-21 05:03 UTC, ventsislav mladenov

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 ventsislav mladenov 2013-06-21 05:03:15 UTC
Working with Interfaces failing code completion in the evaluator and in watch pad
In following example if you try to evaluate a variable "t.Prop1" there will be no code completion.

using System;

namespace Test2
    class MainClass
        public static void Main(string[] args)

            Test t = new TestImp();
            t.Prop1 = "Hello World!";

    public interface Test
        string Prop1 { get; set; }

    public class TestImp : Test
        public string Prop1 { get; set; }

        public string Prop2 { get; set; }

        public string Prop3 { get; set; }
Comment 1 ventsislav mladenov 2013-06-21 05:03:57 UTC
Created attachment 4173 [details]
Test program source
Comment 2 Jeffrey Stedfast 2013-06-21 13:04:43 UTC
This seems to be a bug in the code-completion logic and not specific to the debugger
Comment 3 Mike Krüger 2013-06-21 18:22:29 UTC
But it works in the editor ... therfore the debugger must use the completion logic  wrong somehow.
Comment 4 Jeffrey Stedfast 2013-06-21 18:35:00 UTC
Then can you take a look? Because I don't know the API well enough to see the problem.
Comment 5 Mike Krüger 2013-06-22 02:51:51 UTC
I'll try :)
Comment 6 Jeffrey Stedfast 2013-07-25 16:13:32 UTC
fixed in git master