Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

lambda expressions in immediate window for VS2015

I am running Visual Studio 2015, where people claim that lambda expressions are supported in immediate window, watch and other places. But that does not work for me. I created a new console application with the following code:

static void Main(string[] args) {     var list = new List<int> {1, 2, 3, 4, 5, 6, 7}; } 

And then tried some simple lambdas in immediate window and watch as can be seen here: enter image description here

And as you can see, it gives me "Expression cannot contain lambda expressions". I've looked in tools -> options -> debug settings but could not find anything related to the issue. The version I am running is VS2015 Enterprise, 14.0.24720.00 Update 1 What could be causing this issue?

like image 365
Stenkross Avatar asked Apr 11 '16 21:04

Stenkross


People also ask

What does => mean in LINQ?

The => operator can be used in two ways in C#: As the lambda operator in a lambda expression, it separates the input variables from the lambda body. In an expression body definition, it separates a member name from the member implementation.

Which is faster LINQ or lambda?

There is no performance difference between LINQ queries and Lambda expressions.

What is lambda expression in C# used for?

Lambda expressions in C# are used like anonymous functions, with the difference that in Lambda expressions you don't need to specify the type of the value that you input thus making it more flexible to use. The '=>' is the lambda operator which is used in all lambda expressions.

What is lambda expression in C# with example?

The expression num => num * 5 is a lambda expression. The => operator is called the "lambda operator". In this example, num is an input parameter to the anonymous function, and the return value of this function is num * 5 . So when multiplyByFive is called with a parameter of 7 , the result is 7 * 5 , or 35 .


1 Answers

This definitely works for me, looks like when I tick either Use Managed Compatibility Mode or Use the legacy C# and VB expression evaluators it stops working. Ensure those are unchecked.

enter image description here

like image 195
Tom Avatar answered Sep 28 '22 02:09

Tom