Route ambiguity in AttributeRouting
I'm trying to create two different routes on two different action methods like this:

    [GET("/project/create")]
    public ActionResult Create()

    [GET("/project/{projectId}")]
    public ActionResult Details(int projectId)

The problem is that when i navigate to /project/create, I'm routed to the Details page, which fails because projectId is not an int.

I realise that I could change the Details route to something like `/project/{projectId}/details` but I would like for it to work the other way.

Also a solution could be to make projectId a string, and internally redirect to the Create action if projectId == "create" but that would feel awful.

I am using [AttributeRouting][1] for this. 


  [1]: https://github.com/mccalltd/AttributeRouting
Route ambiguity in AttributeRouting
===

I'm trying to create two different routes on two different action methods like this:

    [GET("/project/create")]
    public ActionResult Create()

    [GET("/project/{projectId}")]
    public ActionResult Details(int projectId)

The problem is that when i navigate to /project/create, I'm routed to the Details page, which fails because projectId is not an int.

I realise that I could change the Details route to something like `/project/{projectId}/details` but I would like for it to work the other way.

Also a solution could be to make projectId a string, and internally redirect to the Create action if projectId == "create" but that would feel awful.

I am using [AttributeRouting][1] for this. 


  [1]: https://github.com/mccalltd/AttributeRouting