did someone tried this code library and have opinion about it? http://code.msdn.microsoft.com/exprserialization
10x
A:
It's used in the client proxy for ADO.NET Data Services for performing LINQ queries against a RESTful service and having that query serialized and executed on the service. Works great in my experience.
If you want to test its usefulness, try out an ADO.NET Data Service.
Anderson Imes
2009-06-03 16:11:43
i think we're not talking about the same thing.the expresion tree serialization project uses no WCF service.
Tamir
2009-06-04 06:36:04
We are indeed talking about the same thing. This is an *application* of expression tree serialization - the serialized expression tree is used to create a URL for RESTful data retrieval. I thought you might like to see a practical application of expression tree serialization. (hopefully you aren't serializing expression trees just for the sake of serializing them :) )
Anderson Imes
2009-06-04 16:14:40
the samples MS provide for the ExpressionTreeSerialization project not showing any WCF service. they take IQueryable object, serialize it into new object, send to the server - no matter how (WS, WCF ect) and deserialize them back to IQueryable, execute the query and return the IEnumerable to the client. i think this is different thing from the Astoria project
Tamir
2009-06-08 10:32:44
You are right. My mistake. Good luck!
Anderson Imes
2009-06-15 19:36:42
Well, you do need WCF service, but not RESTful, and this is for reflecting the entities from the service.Anyway, there is no connection between the ADO.NET Data Services(Astoria) and the ExpressionTreeSerialization.Finally, this library wasn't helpful for me as it's not supports EF, only LINQ2SQL.Thanks anyway!
Tamir
2009-06-18 10:22:47
+1
A:
I have found that it cannot serialize custom closures and I am currently writing my own binary serializer. With that said the fact that expression tree serialization was not included in .net 4.0 is extremely dissapointing.
Steve
2009-07-29 00:46:22
+1
A:
I'm using this library to serialize/deserialize "linq to object" queries. The library doing this pretty well. There was some problems, but I was able to fix them due to the library's open source. The problem that it's not supported any more.
Kamarey
2009-09-23 07:44:05
I guess this because of it refer to LINQ To SQL with DataContext instead of ObjectContext (in the implementation of the Entity Framework).Anyway, we solved this issue by creating dynamic query that the client side developer can create "Query" object, add "Condition" object to it's Query.Conditions collection etc' very similar to the way it's implemented in few other libraries (e.g. webdev)Thank you for sharing.Tamir.
Tamir
2009-09-23 13:41:47
A:
Security aspects of this library are really scary to me. It's almost like executing an arbitrary code that came from configuration or through a request.
Vladimir Lifliand
2010-03-13 04:18:26