Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New names for nuget packages #6

Open
congysu opened this issue Jun 23, 2015 · 2 comments
Open

New names for nuget packages #6

congysu opened this issue Jun 23, 2015 · 2 comments

Comments

@congysu
Copy link
Contributor

congysu commented Jun 23, 2015

@markdstafford proposed new names for nuget packages. Let us know your thoughts. Thanks.

New name Existing name
OData v3 Core (ODataLib) ODataLib for OData v1-3
OData v3 Core (EdmLib) EdmLib for OData V1-3
OData v3 Core (Spatial) System.Spatial for OData V1-3
OData v3 Client WCF Data Services Client for OData v1-3
OData v3 Server (Web API) Microsoft ASP.NET Web API 2.2 for OData v1-3
OData v4.0 Core (ODataLib) ODataLib
OData v4.0 Core (EdmLib) EdmLib
OData v4.0 Core (Spatial) Microsoft.Spatial
OData v4.0 Client OData Client for .NET
OData v4.0 Server (Web API) Microsoft ASP.NET Web API 2.2 for OData v4.0
OData v4.0 Server (RESTier) RESTier
@dingeins
Copy link
Contributor

We should write a blog post for it. This repo has too few subscribers.

The "OData vx Client" and "OData vx Server" seems a little ambiguous. It may make people think they're client app & server app instead of client lib / server lib.

I'd propose "OData vx Client Lib" / "OData vx for Client".

@pascalberger
Copy link

I assume this is about the package title? Would IDs stay the same?

In my opinion IDs at the moment are even more confusing than the titles (eg. Microsoft.AspNet.WebApi.OData for v3 and Microsoft.AspNet.OData for v4).

What about version numbers? Microsoft.AspNet.WebApi.OData is currently at 5.5 and Microsoft.AspNet.OData 5.6. Do they in some way correlate (meaning OData v3 5.5 correlates to OData v4 5.5)? Or shouldn't they better be versioned independently

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants