Odata client V4 compilation error

(0) Share

Report

Posted on by Community Member

Hi,

I am getting below error after generating Odata client proxy v4 on compilation, any suggestion whats need to be done ?

I have created an DataEntity wanted to access in C# as one of the step is to generated Odata client proxy I have install and generated but after VS restarted as the process but when I complied the VS project getting below error

Error CS0234 The type or namespace name 'EdmxReader' does not exist in the namespace 'Microsoft.OData.Edm.Csdl' (are you missing an assembly reference?)

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Sort by

Lauras U 959 on at

Like (0)

Report
Copy link

Link copied!

Had similar problem. Solved by downgrading *Odata* NuGet packages from 7.4.0. to 6.19, updating simple.odata.client to 4.29. Then regenerated Odata.cs file by saving Odata.tt

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Same problem here. Trying to downgrade.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Error CS0117 'CsdlReader' does not contain a definition for 'Parse'

Was this reply helpful? Yes No
Piyush Adhikari 2,546 on at

Like (0)

Report
Copy link

Link copied!

Sir

Can you share me the link which you are following for consuming Odata services? i need to do the same.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Solution is next:

1. Make sure you are on Framework 4.6.1

2. Add Nuget Extensions & Tools for Connected services

3. Connect the service to D365FO which will use T4

4. Compilation or reference errors occur;

5. Add Microsoft.Data.OData version 5.8.3 and add Microsoft.Client 7.4.4 through Nuget.

6. Also verify Microsoft.Edm and Microsoft.Odata referenced to your project

7. Now rename EmdlReader to CsdlReader in the generated project.

8. Now you can compile.

Can happen that on point 7 your VS crashes, better is to use NotePad outside VS.

Was this reply helpful? Yes No