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

asp.net v5 and coreclr #264

Closed
grahamehorner opened this Issue Jul 10, 2015 · 7 comments

Comments

Projects
None yet
2 participants
@grahamehorner
Copy link

grahamehorner commented Jul 10, 2015

please consider targeting the coreclr and/or supporting asp.net v5

@lewischeng-ms

This comment has been minimized.

Copy link
Contributor

lewischeng-ms commented Jul 13, 2015

@grahamehorner Thanks for the suggestion. We have already supported that in ODataLib, EdmLib and Microsoft.Spatial. Please refer to #97.

@lewischeng-ms lewischeng-ms self-assigned this Jul 13, 2015

@grahamehorner

This comment has been minimized.

Copy link

grahamehorner commented Jul 13, 2015

@lewischeng-ms great news; are you planning to publish the nuget packages on the aspnet myget feed? and keep in sync with the release of beta packages. The reason for asking is I'd love to get odata working on the Raspberry PI v2 under dnx arm. keep up the great work; it great to see these things evolving in public forums 👍

@lewischeng-ms

This comment has been minimized.

Copy link
Contributor

lewischeng-ms commented Jul 13, 2015

@grahamehorner Thanks:P The reasons why we didn't put packages into aspnet myget are that: we do not have any dependency on aspnet beta packages; OData do not belong to aspnet product line. You can directly download the latest package from nuget.org to play with .net core 5. By the way, we will first close this issue. If you have any further problem, welcome to open new issues to report them:)

@grahamehorner

This comment has been minimized.

Copy link

grahamehorner commented Jul 13, 2015

@lewischeng-ms isn't the odata controller part of the odata.net if so I would have thought is has a dependency on the aspnet mvc/api and therefore the streamlining of code in asp.net v5 and mvc 6 would have an impact? I'm currently have difficulty with asp.net beta6 and odata namespaces getting confusing etc. which version namespace package should I be referencing? for clr & coreclr support?

@lewischeng-ms

This comment has been minimized.

Copy link
Contributor

lewischeng-ms commented Jul 13, 2015

@grahamehorner odata.net is just a set of .NET libraries that implement OData v4 protocol. It is the basic building block of many OData products. One of them is called OData Web API (https://github.com/OData/WebApi) which is built upon odata.net and ASP.NET Web API (integrated into MVC 6 now) to help users easily build OData service using Web API (or MVC). The key concept of OData Web API is what you mentioned as ODataController. This kind of controller can handle OData requests.

If you would like to use odata.net in ASP.NET 5, please directly add reference to the packages (Microsoft.OData.Core, Microsoft.OData.Edm and Microsoft.Spatial) in VS2015.

But I guess that's not your real intention. If you want to build an OData service in ASP.NET 5, you can use our latest alpha version of OData Web API (http://odata.github.io/WebApi/#07-07-6-0-0-alpha1). The alpha version was designed specifically for ASP.NET 5.

Thanks.

@grahamehorner

This comment has been minimized.

Copy link

grahamehorner commented Jul 13, 2015

@lewischeng-ms many thanks for the clarification; all becomes clearer now 👍

@lewischeng-ms

This comment has been minimized.

Copy link
Contributor

lewischeng-ms commented Jul 14, 2015

@grahamehorner You are welcome. Please don't hesitate to ask any question.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment