I think that for an strange reason, Expr.Invoike in one side doesn't break. I've tests on that here: http://linqspecs.codeplex.com/SourceControl/changeset/view/f8b332648229#LinqSpecs.IntegrationalTests%2fAndQueriesFixture.cs <http://linqspecs.codeplex.com/SourceControl/changeset/view/f8b332648229#LinqSpecs.IntegrationalTests%2fAndQueriesFixture.cs> http://linqspecs.codeplex.com/SourceControl/changeset/view/f8b332648229#LinqSpecs.IntegrationalTests%2fSampleQueries%2fByAlbumTitle.cs
<http://linqspecs.codeplex.com/SourceControl/changeset/view/f8b332648229#LinqSpecs.IntegrationalTests%2fSampleQueries%2fByAlbumTitle.cs>But yes, i think you are right, ant it should works calling invoke on both sides. 2011/1/7 Fabian Schmied <[email protected]> > I'm not sure if the workaround you've posted will always work: you're > still using Expression.Invoke in those cases where the parameters are > not the same for both expressions. I believe that those cases would > still cause the exception described by the original poster > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
