How can I pass a lambda expression to a WCF service?
Solution 1:
We have to solve this problem in LINQ-to-Just-About-Everything. For example, when doing LINQ-to-SQL:
var results = from c in customers where c.City == "London" select c.Name;
somehow the content of the lambdas c=>c.City == "London"
and c=>c.Name
need to end up on the SQL server in a form the server understands. Clearly we cannot persist the lambdas to the server.
Instead what we do is turn the lambdas into Expression Trees, analyze the expression trees at runtime, build an actual string of SQL out of it, and send that string to the server for processing.
You can do the same thing. Create a query language for your server. On the client side, turn the lambdas into expression trees. Analyze them at runtime, turn the result into a string in your query language, and then send the query to the service.
If you're interested in how this works in LINQ, the LINQ-to-SQL architect Matt Warren has written a long series of blog articles on how to do it yourself:
http://blogs.msdn.com/b/mattwar/archive/2008/11/18/linq-links.aspx
Solution 2:
Perhaps a dynamic query would work in your situation?
http://weblogs.asp.net/scottgu/archive/2008/01/07/dynamic-linq-part-1-using-the-linq-dynamic-query-library.aspx
You would pass a where clause string to the service which would validate and convert it to an expression
Solution 3:
WCF doesn't offer this out of the box. You would essentially have to write a custom serializer that took lambda expressions and turned the expression tree into a serializable piece of data.
This is how WCF DataServices works. You use lambdas in your client code, it decomposes those lambda expressions into strings which it passes on the querystring to the data service which then turns the string back into a lambda which it applies to a IQueryable on the server side.
Doable, but you will have to to write a lot of custom serialization code for this. Also, let's be clear, these would be lamdba expressions, not full lambda methods containing random code that could ever be executed on the server side.