Bug 6289 - Cannot invoke extension methods in the immediate window
Summary: Cannot invoke extension methods in the immediate window
Status: RESOLVED DUPLICATE of bug 4610
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Debugger ()
Version: unspecified
Hardware: PC Mac OS
: High major
Target Milestone: ---
Assignee: Jeffrey Stedfast
Depends on:
Reported: 2012-07-25 19:05 UTC by Alan McGovern
Modified: 2012-07-26 15:13 UTC (History)
1 user (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-25 19:05:04 UTC
I'd love it if this worked, but I don't know how feasible it would be. I frequently end up in a scenario where I want to view the intermediate output of a chained linq statement but I cannot do so by copying/pasting parts of the statement into the immediate window. For example

public static void PrintStuff (List<Foo> list)
     Console.WriteLine (list.Select (f => f.Value).Where (a => a.Bar == 16).Select (f => new Barr (f));

Sometimes i would want to type this in the immediate window:

list.Select (f => f.Value).Where (a => a.Bar == 16).ToArray ();
Comment 1 Jeffrey Stedfast 2012-07-26 15:13:52 UTC

*** This bug has been marked as a duplicate of bug 4610 ***