Improve the log message when we a route matches but cannot find an controller/action.

[kichalla]

Following is how the log looks like...

Suggestion: We can clearly mention what action we were looking for and in which controller. Note that I enabled debug logging and probably being very descriptive is not bad.

Example: No action with name 'Foo' found on controller 'Namespace.Home''

[Eilon]

@rynowak does this information even exist such that we can log it? We surely know the controller and action tokens but could we reliably say what controller type/namespace it was?

[javiercn]

I don't think you can do this in a general/accurate way. There are many cases in which the action might be there but not match due to an httpmethod constraint, an area constraint or any other constraint that the user has assigned to the route (for which you definitely not have text for)

[rynowak]

does this information even exist such that we can log it?

We can log the route values - that should be good enough

There are many cases in which the action might be there but not match due to an httpmethod constraint

This isn't that case. We give better logging output already for that case

[khellang]

Should this rely on RouteValueDictionary's ToString?

[felipepessoto]

I plan to work on it

[programatt]

Is there a reason why this wasn't closed? It looks like it was fixed with the PR that @juunas11 had merged in.

[Eilon]

@programatt I believe you are correct.

@kichalla can you confirm?

[kichalla]

d44c9ae