Microsoft.OData.Core和Microsoft.Data.OData之间的区别 [英] Difference between Microsoft.OData.Core and Microsoft.Data.OData

查看:161
本文介绍了Microsoft.OData.Core和Microsoft.Data.OData之间的区别的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在启用OData的Web Api上工作.我从参考(仅提及问题的相关dlls )

I am working on Web Api with OData enabled. I started working by referring to (only the relevant dlls to the question are mentioned)

Microsoft.AspNet.WebApi.OData
Microsoft.Data.OData
Microsoft.Data.Edm
System.Spatial

但是当我发现默认情况下OData区分大小写时,我正在寻找不区分大小写的解决方案,并且我已经阅读了几篇文章 ODataLib 6.7. 0发布,然后最终进入nuget包 Microsoft.OData.Core 6.9.0 似乎可以解决我的问题. 我的困惑开始了 ,它在不同的命名空间下有自己的与馆藏相关的库

But when I found out OData is by default case-sensitive, I look for a solution of case insensitive and I have gone through few post Support OData Uri case insensitive parse & ODataLib 6.7.0 Release then finally landed into nuget package Microsoft.OData.Core 6.9.0 which seems to be solving my problem. Here my confusion starts, It has its own collection related libraries under different namespace

Microsoft.OData.Core-----------VS------Microsoft.Data.OData
Microsoft.OData.Edm------------VS------Microsoft.Data.Edm
Microsoft.Spatial--------------VS------System.Spatial

以上类似的库之间有什么区别,我们应该在另一个上使用?在我的类似情况下,可以使用 Microsoft.OData.Core 代替正在解决区分大小写问题的 Microsoft.Data.OData ?

What is difference between above similar libraries, where we should use one upon another? In similar cases of mine, Microsoft.OData.Core can be use instead of Microsoft.Data.OData which is solving case sensitive issue?

推荐答案

1.关于名称空间,

Microsoft.Data.OData
Microsoft.Data.Edm
System.Spatial

OData 3.0版规范的实现. Nuget上的软件包名称以 OData v1-3 结尾.例如: OData v1-3的ODataLib

are the implementation of OData Version 3.0 Spec. The package name on Nuget end with OData v1-3. For example: ODataLib for OData v1-3

Microsoft.OData.Core
Microsoft.OData.Edm
Microsoft.Spatial

OData版本4.0规范的实现. Nuget上的软件包名称不包含version.例如: ODataLib

are the implementation of OData Version 4.0 Spec. The package name on Nuget don't contain version . For example: ODataLib

2.关于不区分大小写的

Web API OData将在5.4版本中支持不区分大小写,不合格的函数/操作调用和免费的Enum前缀.

Web API OData will support case-insensitive, unqualified function/action call and Enum prefix free in the 5.4 release.

这里是您可以参考的简单示例.

Here's a simple example you can refer to.

源代码移至: Github上的WebAPI OData

您可以从每晚构建中获取二进制文件.

And you can get the binary from nightly build.

这篇关于Microsoft.OData.Core和Microsoft.Data.OData之间的区别的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆