I have heard of similar issue and it was caused by referencing different namespace, which is quite similar in its name. Instead of using System.Web.Mvc.Routing.Constraints; they brought in using System.Web.Http.Routing.Constraints namespace in the RouteConfig class. Could you check whether this is the same case?