We're really excited about this control as it will really push us forward in a lot of heavy scenarios where "normal" programming falls apart. I have to echo a previous post that documentation should be a priority. I think people will simply skip over this if documentation isn't present.
The thing I'm fighting is this. We have in our N-Tier architecture a DbContext from a CodeFirst EF model and not a straight ObjectContext. The fluent api exposed by the DbContext is something we've been using for nearly 6 months now. I'm getting the underlying ObjectContext from the DbContext using the code below, but I am getting a Query Object Not Found error no matter which table I attempt to tie to. My guess is that, in reversing a DbContext back to an ObjectContext, I'm losing a lot of my definitions.
1. Do you support DbContexts?
2. If not (which I suspect is the answer), how could I use this control with a DbContext?