Linq generic Expression in query on “element” or on IQueryable (multiple use)?

You won't be able to use that in a query expression, but your second code snippet (calling Where explicitly) should be okay For the second query it's hard to say without seeing OtherFunctionThatCallsJoinByDateCheck basically you won't be able to put it in a query expression, but if you can pass the query to this other function, that may work.

You won't be able to use that in a query expression, but your second code snippet (calling Where explicitly) should be okay. For the second query it's hard to say without seeing OtherFunctionThatCallsJoinByDateCheck - basically you won't be able to put it in a query expression, but if you can pass the query to this other function, that may work.

Ok, The Idea is that I have a lot of code that must call this condition, and It has to be used as a "standard" – Bogdan Maxim May 12 '10 at 14:25 @Bogdan: The problem is that query expressions automatically convert the code within them into lambda expressions, which for LINQ to SQL are then converted into expression trees. You don't want an expression tree containing a call to your helper method - you want the helper method itself to be called. That simply doesn't work in query expressions.

– Jon Skeet May 12 '10 at 14:47.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.