Structuring MVC Routes - asp.net-mvc-3

Question

I have the following url structure, and just trying to figure out the best Routes to configure.
EDIT: Added more url's
/cars/{name} (shows general information about a car)
/cars/{name}/models (shows a list of models for a particular car)
/cars/{name}/models/{id} (shows a specific model for a particular car)
/cars/{name}/models/edit (add a new model which would be an action)
/cars/{name}/models/{id}/owners (a list of owners for a particular model)
/cars/{name}/models/{id}/owners/create (add a new owner)
So far, I have
routes.MapRoute(
name: "CarReleases",
url: "cars/{name}/models/{id}",
defaults:
new
{
controller = "Releases",
action = "Index",
id = UrlParameter.Optional
}
);
This works if I use /cars/{name}/models, but obviously, I don't have the action available for the models page. Do I have to create a new route map for this situation?
I also have the CarController, which is mapped as follows:
routes.MapRoute(
name: "Cars",
url: "cars/{name}/{action}",
defaults: new { controller = "Cars", action = "Details", id = UrlParameter.Optional }
);
As you can see, I have a general mixture of actions and dynamic requests. Bit confused the best way to put this into maproutes.

Answer 1

Order your routes from the most specific to the least specific. In my example all actions are mapped to the controller Cars; however, you may separate them. For example:
Owners:
routes.MapRoute(
name: "owners",
url: "cars/{name}/models/{id}/owners/{action}/{ownerId} ",
defaults: new { controller = "Cars", action = "OwnerIndex", id = UrlParameter.Optional, ownerId = UrlParameter.Optional }
);
Models:
routes.MapRoute(
name: "models",
url: "cars/{name}/models/{action}/{id}",
defaults: new { controller = "Cars", action = "ModelIndex", id = UrlParameter.Optional }
);
Cars:
routes.MapRoute(
name: "Cars",
url: "/cars/{name}/{action}/{id}",
defaults: new { controller = "Cars", action = "Index", id = UrlParameter.Optional }
);
Notice the default action was changed to Index so it lists all when you omit the action and Id (you may need to change it if you decide to keep them all in one controller)
Regarding your question whether you should keep them in one single controller, I think that's fine unless you would like to separate admin functions (edit, delete, etc) from viewing. In any case you can still have them in one controller and just add the Authorize attribute.
[Authorize(Roles = "admin")]
public ViewResult Delete(int id){}