The point is don't come to a public discussion started by the author of that tool and piggy back yours on while saying not to include his.
" If the ASP.NET team wants to provide a better routing solution, it should be a really good solution, better than AttributeRouting."
You mean like your project? The advantage with open source is the commit can go in, and be worked on quite a bit before the next release. IE 'Any project' can be used as a base. Yours, AttributeRouting, the stack overflow source etc. Three
'strong' routing projects that can surely have a good basis.
So let's try a helpful conversation:
Whats wrong with attribute routing? Aspects to get to where we want make sense to be applied to a method.
The constraint syntax is awesome. Your CustomRoute class seems to serve a similar purpose, so whats the main difference?
Whats a weakness of it? Whats a strength of yours? Whats a weakness of yours?
In yours I see a convention created in a place where ordering of routes is very important. A developer relies on black box route creation behavior to hope the order of routes is correct I didn't see on your main wiki page if you can specify the order, so
we 'hope' the routes are created in the proper order. The same goes for AttributeRouting but we can specify an order.
In your project what about optional parameter and route constraints? All of the information surely isn't available in code to make a proper route constraint by convention. You can 'half guess it' and it may work a good portion of the time, but how do you
know the business rules for say a FirstName or a default value for Page? So then you are back to using a [CustomRoute()], no?