You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I followed an instruction to generate an automatic code, based on my OData server's metadata. Code generation was completed, but two kind of error occurred:
1. invalid variable name, due to an extra space. (I fixed this manually by replacing space with underscore. This post is not about this bug)
2. The type or namespace name of 'UInt16', 'UInt32', and 'UInt32' don't exist in the namespace 'A.B.C'. Their UnderlyingType are Edm.Int32, Edm.Int64, and Edm.Decimal, respectively (See below image).
Below screenshot illustrate errors from my VS 2022. It is repetitive, but shows where the errors occurred:
So I wonder, if OData's code generator can handle unsigned data type? Is there anything I can do to fix this?
Describe the bug
I followed an instruction to generate an automatic code, based on my OData server's metadata. Code generation was completed, but two kind of error occurred:
1. invalid variable name, due to an extra space. (I fixed this manually by replacing space with underscore. This post is not about this bug)
2. The type or namespace name of 'UInt16', 'UInt32', and 'UInt32' don't exist in the namespace 'A.B.C'. Their UnderlyingType are Edm.Int32, Edm.Int64, and Edm.Decimal, respectively (See below image).
Below screenshot illustrate errors from my VS 2022. It is repetitive, but shows where the errors occurred:
![odata_generated_code_namespace_error](https://private-user-images.githubusercontent.com/10466724/321295708-6390d056-9b2b-4588-8a52-9d625184a5a7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzg5MTYxMTMsIm5iZiI6MTczODkxNTgxMywicGF0aCI6Ii8xMDQ2NjcyNC8zMjEyOTU3MDgtNjM5MGQwNTYtOWIyYi00NTg4LThhNTItOWQ2MjUxODRhNWE3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA3VDA4MTAxM1omWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI3OGFjMDYxNzRlN2E5MjFlNDY0MGYzNGE5Yjk5NDFjYTQ3ZTE3MDI2NmE0NjEzODhlM2U4NGU4ZGU3MGQ0NmImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Q2HYlg5K1W5avDmlRp3lsxp0ceBrhwFDCjDdwrZJr7A)
So I wonder, if OData's code generator can handle unsigned data type? Is there anything I can do to fix this?
Version of the Project affected
ODataConnectedService 2022+ version: 1.0.2
VisualStudio Enterprise 2022 Version v17.8.6
Microsoft.Odata.Client v7.20.0
To Reproduce
I just followed the Creating a sample client application using OData Connected Service, then all errors are in the default Reference.cs file.
Expected behavior
No error in namespace
The text was updated successfully, but these errors were encountered: