EntityFramework is using the wrong data context [closed]

Question

Closed. This question is not reproducible or was caused by typos. It is not currently accepting answers.

---

This question was caused by a typo or a problem that can no longer be reproduced. While similar questions may be on-topic here, this one was resolved in a way less likely to help future readers.

Closed 8 years ago.

Improve this question

I have an assembly data project in my solution that is being consumed by a different project. The data project contains three different edmx entries.

I'm calling a function import in one, but inside the edmx.cs I'm receiving an error on the calling line:

return ((IObjectContextAdapter)this).ObjectContext.ExecuteFunction

((IObjectContextAdapter)this).ObjectContext

is returning the type of a different context entirely! Thus it cannot find the function I'm calling.

Has anyone seen this behavior before? I don't know why it would be in one context and yet return the other type when the ObjextContext is checked.

Answer 1

A foolish mistake on my part. My connection string in the consuming project was pointing to the wrong csdl. The code compiles fine, you can update from the model perfectly, but it will break at runtime when the consuming project's config is used. Even though you can trace into the edmx.cs file for your data project, it will cast to the other model on the execution line.