The previous fix for #67 hid rather than fixed the problem and caused new issues for non-area controllers.
This fix reverts the previous edit and amends ResolveControllerType instead.
This should now allow type resolving properly in the following cases
*A non-area route provides non-default namespaces
*Non-unique controller names appear inside and outside of an area
Problems will be caused in the following case:
*When non-area routes are to check only within a given namespace and not the defaultnamespaces
This is a much less common edgecase than either above case, it is bucking the "convention over configuration" view of MVC so comes with an expectation of more potential issues.