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

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 – 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.

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

dirq — Thu, 06 Dec 2012 13:39:37 GMT

Thanks so much for the quick updates. You guys are flyin. I'm looking for $inlineCount support for use in the Infragistics IgniteUI grid. Any good resources on putting that in myself with the current webAPI abilities?

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

MichaelD! — Thu, 06 Dec 2012 00:47:54 GMT

Wow... I have spent the past few hours catching up on this project and I have to say: Alex D James, you are my HERO! :) Thanks for being super responsive, attentive and *massively* thorough on these posts. I can only imagine how irritating some of these comments/bug reports can be.

This is an amazing project. I am a fan. Goodbye RIA Services. :) Please do keep up the amazing work, Alex!

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

Jake Heidt — Mon, 03 Dec 2012 22:42:08 GMT

I've run into an issue getting some specific entities up and running on odata/webapi. For the most part everything runs great, but I have a hierarchy of entities that have composite keys - think something like { county number, town number } or { ingredient , recipe }

Is there a relatively easy way to get all the URL goodies that are baked into the currently expected URLs that take id, to take multi-part keys in the id? stuff like /books(15) ie: /books(15,1337) ?

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

mj1856 — Thu, 29 Nov 2012 22:47:58 GMT

@RaghuRam - Thanks, I like the idea of inheriting it into my own attribute. Thanks. (BTW - I hadn't updated my MSDN profile yet to match my others. I still don't like how the "display name" has to be unique. Prevents me from using my real name)

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

RaghuRam — Thu, 29 Nov 2012 19:35:42 GMT

@mj123451

you could enable it by using the extension method we added EnableQuerySupport.

config.EnableQuerySupport(new QueryableAttribute { HandleNullPropagation = HandleNullPropagationOption.False });

The side-effect is that query-composition is enabled for all actions that return IQueryable<T>.

An alternative way is to inherit the QueryableAttribute and in the ctor set HandleNullPropagation to False like,

public class NonNullPropagationQueryableAttribute : QueryableAttribute

{

public NonNullPropagationQueryableAttribute()

{

HandleNullPropagation = HandleNullPropagationOption.False;

}

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

Alex D James — Thu, 29 Nov 2012 19:20:07 GMT

@mj123451 (great name BTW).

I'm not sure on this. Queryable is registered as an ActionFilter so there is a chance you can do this globally. I've sent an email to people who know this code better than me, hopefully they'll weigh in soon!

-Alex

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

mj1856 — Thu, 29 Nov 2012 16:52:25 GMT

@Alex - Can you expose a singleton for setting the default options on Queryable? I saw your last post that includes the options for null propagation handling. There are many more LINQ providers than just EF, L2S and L2O. For example, we can use WebApi with OData to query against RavenDB with their LINQ provider. But for it to work properly, I have to set HandleNullPropogationOption.False on every single controller. There should be a simpler way to set the default globally.

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

Alex D James — Tue, 27 Nov 2012 01:08:49 GMT

@Szymon

Add this Nuget source - www.myget.org/.../aspnetwebstacknightly