Is the route debugger only for use with traditional routing?
I get a lot of routes if I have routing attributes set and I'm not seeing how the tool helps. With attribute routing, every route matches with the 2nd line down in the matrix and it has 'n/a' for each column to the right of 'True'. I.E. it doesn't show a match for the routes specified for each Controller/Action pairing, only that undefined row in the matrix (and of course *catchall).
Since the book suggests new applications should use Attribute routing, does the debug tool lose its usefulness, or is there a different tool to use, or a different setup for this tool to make it work more effectively with Attribute routing?
Thanks for any insight.