I like the right part, but I wish the compiler would just…figure out the left part. We’ve just ignored it for now, accepting that no matter what we do, it’ll be ugly. Just trying to find the least ugly way…

Expr.Method>(o => o.SomeMethod);

Given all the generic parameters you have to specify, that may not be any better. Just thought I would throw that out there. I did a little test and it seemed to work. Here is the code:

public static class Expr
{
public static string Method (Expression> methodExpression)
where TDelegate : ICloneable,ISerializable //you cannot limit a generic parameter to be a Delegate, but this gets us closer.
{
return GetMethodName((UnaryExpression)methodExpression.Body);
}

public static string Method(Expression> methodExpression)
{
return GetMethodName((UnaryExpression) methodExpression.Body);
}

private static string GetMethodName(UnaryExpression unaryExpression)
{
var methodCallExpression = (MethodCallExpression)unaryExpression.Operand;
var constantExpression = (ConstantExpression)methodCallExpression.Arguments[2];
var method = (MethodInfo)constantExpression.Value;

return method.Name;
}
}