与GetVirtualPath匹配的路由

不幸的是,我认为生成url的逻辑不能很好地处理静态url。我相信你能做的一件事是:

routes.MapRoute(
    "Branding",
    "{controller}/bar.css",
    new { controller = "DynamicContent", action = "CSS" },
    new {controller="foo"}
  );

试试看。

也就是说,如果其他人遇到了相同的问题,我可以通过反转路由顺序来克服它,首先使用NotEqual约束添加更模糊的默认路由,以确保DynamicContent路由在需要时被命中。

routes.MapRoute(
  "Default",
  "{controller}/{action}/{id}",
  new { controller = "Account", action = "Index", id = UrlParameter.Optional },
  new { controller = new NotEqual("DynamicContent") }
);

routes.MapRoute(
  "Branding",
  "foo/bar.css",
  new { controller = "DynamicContent", action = "CSS" }
);

对于那些想知道NotEqual是什么的人,我找到了 on a blog .

public class NotEqual : IRouteConstraint
{
  private string _match = string.Empty;

  public NotEqual(string match)
  {
    _match = match;
  }

  public bool Match(HttpContextBase httpContext, Route route, string parameterName, RouteValueDictionary values, RouteDirection routeDirection)
  {
    return String.Compare(values[parameterName].ToString(), _match, true) != 0; 
  }
}