OData v4 Support
Version 4 of OData is released and supported by Web API. (And since WCF Data Services is dead, Web API OData is all we are going to get.)
Please consider support for version 4 OData endpoints.
![](https://secure.gravatar.com/avatar/fbd30e6be361585da1a00018f62ccd12?size=40&default=https%3A%2F%2Fassets.uvcdn.com%2Fpkg%2Fadmin%2Ficons%2Fuser_70-6bcf9e08938533adb9bac95c3e487cb2a6d4a32f890ca6fdc82e3072e0ea0368.png)
-
Enis Bajra commented
+1
-
Mirza commented
+1
-
LinusF commented
Hi Joe, I found an issue in stackoverflow about this Topic:
http://stackoverflow.com/questions/25210661/get-the-odata-catalog-for-web-api-odata-v4-in-xml -
LinusF commented
Joe: Is RestierController an official MS class? I could not find it. My controllers derive from ODataController...
-
LinusF commented
I can deploy the OData service in our intranet only. Therefore you won't have access to it.
When I open the connection in LinqPad I get the error: "The remote server returned an error (404) not found"
When I call the same URL by Chrome I get the correct answer:
{
"@odata.context":"http://reportingggr-data.test.winport.net/odata/flli1/$metadata","value":[
{
"name":"Berichte","kind":"EntitySet","url":"Berichte"
},{
"name":"Produktegruppen","kind":"EntitySet","url":"Produktegruppen"
},{
"name":"BerichtProduktegruppen","kind":"EntitySet","url":"BerichtProduktegruppen"
},{
"name":"Auftraege","kind":"EntitySet","url":"Auftraege"
},{
"name":"Departemente","kind":"EntitySet","url":"Departemente"
},{
"name":"Bemerkungen","kind":"EntitySet","url":"Bemerkungen"
},{
"name":"Kredite","kind":"EntitySet","url":"Kredite"
},{
"name":"Messgroessen","kind":"EntitySet","url":"Messgroessen"
},{
"name":"Nettokosten","kind":"EntitySet","url":"Nettokosten"
},{
"name":"Zielvorgaben","kind":"EntitySet","url":"Zielvorgaben"
}
]
} -
LinusF: I've tested the driver with JSON formatting and a controller derived from RestierController (subclass of ODataController) and it appears to function correctly. What error are you getting?
-
LinusF commented
Joe Albahari added the OData v4 driver to the Connection. But unfortunately this published version has some drawbacks:
- It works only with XML-Atom formatting. The json format produced by normal ASP.NET MVC impemenation (Controller derived from ODataController) does not work with this Driver.
- The password is not hidden -
meancrazy commented
I just released simple OData4 driver: https://github.com/meancrazy/LINQPadOData4/releases
-
SeanJ commented
+1
-
Long Le commented
+10
-
Anonymous commented
I don't migrate my projects to latest versions of EF just because I want to continue to use Linqpad on my actual ODATA connexion.
Please upgrade. ODATA V4 is mature, now -
Evgeniy commented
+1 for OData v4 Support
-
LegeDoos commented
+1
-
Anonymous commented
I think a OData v4 support is a must have ...
-
Jim Daly commented
+1 for OData v4 Support
-
Frank commented
+1 for OData v4 support
-
Marc commented
Today, I use VS to generate my proxies with the TT included with https://visualstudiogallery.msdn.microsoft.com/9b786c0e-79d1-4a50-89a5-125e57475937. I'd love to do this in LINQPAD as it would save me a lot of time. I'd like to have all my OData connections at the same place... It would be nice if it could be supported directly by LINQPAD or if someone could create a custom driver for it (as I'm too lazy to build it myself). I could give it a try if LINQPAD does move in the next few weeks.
-
Anonymous commented
OData v4 support is must have....
-
Patrick Michalina commented
Yea, OData was the #1 reason I use this app. To demo the power of OData and LINQ.
-
Patrick Michalina commented
+1 for v4 support. Linqpad is awesome and would love to be able to add the new OData sources.