I took a slighlty different route

Jul 30, 2014 at 7:54 PM
I was actually about to publish an updated version of something similar that I did a while ago (http://www.balsamicsolutions.com/Blog/Post/2/Full-text-search-in-Microsoft%27s-Entity-Framework) it includes attribute control to enable full text columns and a much different technique for query population. Essentially I do a "pre query" to get the primary key values and then recompose the query as a "contains" for the list. It has the downside of making two queries but the upside of being fully composable . I much prefer the query that your model generates but I cant get it to accept an .Include for related tables. Do you have any insight into that?