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 could forgo deriving from it for sure. I just wanted to create a route that wraps up the exact same thing the framework uses so I wouldn't miss anything going forward. But I figured I'd ask for the simplest thing first. :)
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 could forgo deriving from it for sure. I just wanted to create a route that wraps up the exact same thing the framework uses so I wouldn't miss anything going forward. But I figured I'd ask for the simplest thing first. :)