Meta-Me - All Comments

re: Parsing OData Paths, $select and $expand using the ODataUriParser

Peter LaComb — Wed, 15 May 2013 14:49:12 GMT

As soon as I asked that I realized that the Query may not really return a sequence of type T, so probably No is the answer. We just happen to do a lot of simple filtering with our OData queries.

re: Parsing OData Paths, $select and $expand using the ODataUriParser

Piotr Kołodziej — Mon, 13 May 2013 10:05:55 GMT

Thanks for the blog post. It just so happens that that's the solution we've been looking for as we are implementing custom security mechanism for a different Resource types and we needed a way to efficiently and safely parse the URI.

re: OData in WebAPI – RC release

mcfin — Tue, 19 Feb 2013 02:56:42 GMT

Hi Alex,

I like the way OData handles the keys. However, I may have to implement keys in separate segments. Can you point me to the best way to do this?

"This design means that you don’t like the way OData puts keys in parenthesis (i.e.~/Customers(1)) and would prefer to put keys in their own segments (i.e. ~/Customer/1) then all you need to do is override the DefaultODataPathHandler so that it recognizes this syntax. I’ve tried this personally and doing targeted overloads like this is pretty easy"

re: OData in WebAPI – RC release

psyafter — Mon, 18 Feb 2013 12:45:56 GMT

when using (HttpClient) client.PostAsJsonAsync to endpoint, there is null object recieved to protected override CreateEntity on service side.

re: OData in WebAPI – RC release

swo — Tue, 05 Feb 2013 18:08:49 GMT

Error : Method not found: 'Int32 Microsoft.Data.OData.Query.SemanticAst.QueryNode.get_Kind()'.

orderby/top are working but I get always the error when i use http://localhost:3517/api/Product?$filter=Id eq 1

Is ther a simple easy step by step tutorial to get odata support with simple poco classes. On this page there are to much information for beginners?

re: OData in WebAPI – Microsoft ASP.NET Web API OData 0.2.0-alpha release

SJ — Thu, 24 Jan 2013 05:37:15 GMT

Hi Alex,

Is there an opportunity to implement entity set permissions, ie // Give full access to all of the entities.

config.SetEntitySetAccessRule("*", EntitySetRights.All); as in WCF DS? thx.

re: OData in WebAPI – RC release

Juliano — Wed, 23 Jan 2013 20:35:10 GMT

I figured out the Sample changes (had to update NuGet to the nightly builds)

Do you expect $expand support to be in this release?

If not, is there any way to force the output to expand a navigation property? I understand supporting the generic case is hard, but we have a few specific scenarios in our API specification where $expand is really important...

re: OData in WebAPI – RC release

Juliano — Wed, 23 Jan 2013 00:30:39 GMT

The sample using 0.2.0 build OK. But 0.3.0 doesn't, there's a missing reference to ODataRouteNames. Were those definitions moved somewhere else? I can't find them. How to build Explicit models without it. Thanks!

re: OData in WebAPI – RC release

Philipp Schmid — Fri, 18 Jan 2013 23:36:55 GMT

Where can I find information about the anticipated RTM date for this project?

re: OData in WebAPI – Microsoft ASP.NET Web API OData 0.2.0-alpha release

KC — Mon, 07 Jan 2013 23:05:06 GMT

Is there any reason that writing the code in VB.NET may not allow correct uri routing?

I have two solutions side by side ... identical as far as I can tell, one written in VisualBasic.Net, one in C#.

If I write the code in C# it seems to route to the Get() or Get(Guid key) functions in my apicontroller as you describe but the VB.NET version always routes to the Get() function with no parameters.

GET ~/Products -> Routes to Get()

GET ~/Products(1) -> Also Routes to Get() even though I have a function Get(<FromODataUri>id as integer) available

There may be other issues using VB.NET but this was the simplest failing case I found.