Lambda Expression

When you invoke a delegate, the runtime looks up the methods in its invocation list and calls them in the same order.

So calling a method or methods via a delegate is a late bound operation and therefore slower than calling the method(s) directly.

The primary advantage of lambda expressions is that they allow you to write functions 'inline' rather than as separate methods. The compiler converts them into delegate instances and writes the underlying code for you.

This is useful when you need to pass delegates as arguments to methods, such as in LINQ.

Another aspect of lambda expressions which can be useful is that they allow you to create 'closures'. If you use any 'outer' variables in a lambda expression i.e. variables or parameters which are local to the method in which the lambda expression is defined, then these 'outer' variables are 'captured' and have their lifetime extended to that of the lambda expression itself.

Captured variables are evaluated when the lambda expression is invoked, not when they are captured. However, this can lead to unexpected behavior for those who are unaware (or forget about) this particular feature of lambda expressions. 

BTW, what happened to your previous thread entitled 'synchronized delegate vs method C#'?  I replied to your last post earlier today but then the thread suddenly disappeared so I don't know whether you saw the reply or not.