Edm.ComplexType mapping

[vvdb-architecture]

In some .edmx file, "Edm.ComplexType" is mentioned.

This is translated as

global::Edm.ComplexType

... in the generated code, which doesn't correspond to anything (even though there is a ComplexType in entityframeworkcore.dll, but that's not the same).

For an example, see #434 .

Any workarounds for that? Can Edm.ComplexType be changed to something else that would not issue code generation errors?

[marabooy]

Hi Could you kindly share an example model so I can reproduce this? I am not sure if you mean that we generate code that fails the Edm.ComplexType or you have a type called Edm.Complex type in your model and this causes conflicts with the existing types.

[vvdb-architecture]

Hi Could you kindly share an example model so I can reproduce this? I am not sure if you mean that we generate code that fails the Edm.ComplexType or you have a type called Edm.Complex type in your model and this causes conflicts with the existing types.

See the file in #434

[marabooy]

Hi @vvdb-architecture, I'm looking into how we're handling complex types.

Quick question—are you in control of the service generating the EDMX? From what I understand, any complex type defined in the schema should be eligible to be returned from the function, based on the EDMX. Let me know your thoughts.

[vvdb-architecture]

Hi @vvdb-architecture, I'm looking into how we're handling complex types.

Quick question—are you in control of the service generating the EDMX? From what I understand, any complex type defined in the schema should be eligible to be returned from the function, based on the EDMX. Let me know your thoughts.

Sadly, I'm not in control of anything. I'm just a pawn in the game of life. Or in this case, a victim of an OData service.

[marabooy]

Got it, will see how to best support and figure something out.