Thank you for pointing that out - I know that it might seem like a problem, but you can do two things…

1. Do like Joel and add a route ex. “{controller}/{action}/{id}.{format}”

or

2. Make your own ModelBinder - Haven’t tested this, but I guess it could work.

I didnt realise at first I needed to add the route from your first post. After I did this it worked beautifully.

Dave

I setup an Order method in the home controller, and gave it this signature:

public ActionResult Order(int id)
{
//Stuff returning a view w/ data
}

I then hit http://foo/home/order/23.json

The problem is that when the route is parsed, it interprets 23.json as a string input type for the id argument, and throws an exception. doh!

If I change the argument type to string, it works, except now I have to strip the extension, and cast to an int so my repository can fetch the correct data.

From what I can see of ActionFilters, I don’t think we can strip the extension off before the action is executed.

Anyhow - I’m going to stick with our current methodology using query string parameters (&f=json)

Also - your code uses an extension method on Array (Array.Any) - it would be handy if you could reference where that comes from and/or add it to http://www.extensionmethod.net

Cheers,

Dave

One thing we find we use a lot is a “partial” option. This allows our client side code to call back for rendered HTML for just a part of the page. Something you may want to consider.

Cheers,

Dave