Hi,
I'm the author of AttributeRouting, an open-source project that lets users specify routes using attributes in Mvc, Http.WebHost, and Http.SelfHost scenarios. When generating route for Http.WebHost scenarios, I need to register a custom Route object derived from System.Web.Http.WebHost.Routing.HostedHttpRoute. Currently this object is marked internal, making it impossible to simply hook into the underlying framework.
By contrast, both System.Web.Routing.Route (used by Mvc) and System.Web.Http.Routing.HttpRoute (used by Http.SelfHost) are public and allow me to hook directly into the underlying routing framework.
Cheers,
Tim McCall
Comments: I've found a way around this and do not need anything to change in this regard. I had previously been registering ASP.NET Web API routes directly against the RouteCollection. That was fine in Beta and RC, but for RTM I need to use HttpRouteCollection instead. Internally, your bits will work the HttpWebRoute magic. So, again, I no longer need any changes regarding this issue. FYI.
I'm the author of AttributeRouting, an open-source project that lets users specify routes using attributes in Mvc, Http.WebHost, and Http.SelfHost scenarios. When generating route for Http.WebHost scenarios, I need to register a custom Route object derived from System.Web.Http.WebHost.Routing.HostedHttpRoute. Currently this object is marked internal, making it impossible to simply hook into the underlying framework.
By contrast, both System.Web.Routing.Route (used by Mvc) and System.Web.Http.Routing.HttpRoute (used by Http.SelfHost) are public and allow me to hook directly into the underlying routing framework.
Cheers,
Tim McCall
Comments: I've found a way around this and do not need anything to change in this regard. I had previously been registering ASP.NET Web API routes directly against the RouteCollection. That was fine in Beta and RC, but for RTM I need to use HttpRouteCollection instead. Internally, your bits will work the HttpWebRoute magic. So, again, I no longer need any changes regarding this issue. FYI.