OData客户端库不需要生成客户端代理类? [英] OData Client library that doesn't require client-proxy classes generation?
问题描述
我们目前正在开发一个访问OData服务的AspNet Core项目。我们的"问题"是不断更新提供的元数据信息(不断添加或删除新的实体和字段),因此每次更改时都会生成C#client-proxy
类(我们甚至不知道这些更改何时发生)不是。可行的 
我们需要更动态的东西,不需要生成那些客户端代理类(例如Simple.OData.Client库: https: //github.com/object/Simple.OData.Client)。
Microsoft是否有任何计划开发此类内容或改进当前的OData客户端代码生成器库以便在更有活力的方式?
非常感谢,
Patricia Dieguez
Thermo Fisher Scientific - 服务科学的全球领导者
您好Patricia:
此 论坛
处理与开放规范文档问题相关的请求。
开放式规格可在以下网址找到:
http://msdn.microsoft.com/en-us/library/cc203350.aspx 。
由于您的问题与打开规格文档集,我们建议您跟进以下GitHub Repo - https://github.com/OData/odata.net
< p style ="">谢谢。
Hi,
We are currently working on a AspNet Core project that access OData services. Our "issue" is that the metadata info provided is constantly updated (new entities and fields are constantly added or removed) so generating the C# client-proxy classes every time it changes (we don't even know when those changes happens) is not viable.
We would need something more dynamic that wouldn't require those client-proxy classes to be generated (like for instance the Simple.OData.Client library: https://github.com/object/Simple.OData.Client).
Is there any plan by Microsoft to develop something like this or improve the current OData Client Code Generator library to work in a more dynamic way?
Many thanks,
Patricia Dieguez
Thermo Fisher Scientific - The world leader in serving science
解决方案Hi Patricia:
This forum handles requests related to Open Specifications documentation issues.
The Open Specifications can be found at: http://msdn.microsoft.com/en-us/library/cc203350.aspx.
As your question is not related to the Open Specifications documentation set, we would suggest you to follow up at following GitHub Repo - https://github.com/OData/odata.net
Thanks.
这篇关于OData客户端库不需要生成客户端代理类?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!
查看全文