Improving the Web API routing system–Part 2

The little piece of work I did on the Web API routing system seems to have caught on with a few people on the internet. I’m getting questions on twitter and this blog on a number of things related to the attributed routing addon I created.

So here’s a short list of the questions I got.

 

Have you heard about Attributed routing for ASP.NET MVC?

Ehm, nope I haven’t heard of it before. But apparantly Tim McCall has created a cool framework on top of ASP.NET MVC that allows you to do the very same thing I built, but for ASP.NET MVC. Very cool initiative and looks rock solid.

Some folks asked me to join forces with him to bring my classes into that framework. And yes, I am going to do that as it makes much more sense to merge my stuff into that project. Makes things all the more powerful.

Do you have support for…

There are a number of questions on support for various scenarios:

• Nested collections: I don’t know, haven’t tried it. It might work, it might not. Going to test it though and I will let you know how things are at the moment and what the plan is for supporting it (If I need to do stuff for it).
• Multiple verbs: If you place the HttpRoute attribute on top of a controller, it will support multiple verbs like POST, PUT, DELETE and GET. On method level, you need to specify the verb using the [Http….] attributes (HttpPost, HttpPut, HttpDelete, etc). But I will document this and see if there’s anything I need to do here for additional support.

In the meantime

While I am working out the details of integrating my stuff with the stuff made by Tim McCall, I suggest you either download the sources from the other post on this subject. Or get the Nuget package for the attributed routing code. I published it this afternoon, as it seemed like a good idea to do so at the moment. Keep in mind though, that I will deprecate that package as soon as I integrated my code with Tim his code.

I will keep you posted as things move along