Tim McCall

@friedr1c3 You need to either name your action method `Get...` or include the `HttpGet` attribute alongside the `GET` attribute. There are some workarounds needed for Web API support listed here:...

@devmondo The new AttributeRouting from Microsoft is completely unrelated to this project, and is a ground-up implementation. This is going to be confusing for folks... :(

I think this is unnecessary overhead. If you need the culture/language for filling out url params, you can just pass this info via routeData when generating the links. However, I...

I see. Go ahead and implement a helper and submit the pull request. We'll move on from there. I may give it a crack myself too. Will let you know...

You could also create an extension to the UrlHelper that looks for the appropriate culture. All AttributeRoutes stuff a "cultureName" key/value pair (where appropriate) in the route's data tokens. It...

Hmm, nifty concept. Have you tried using a custom [IRouteConstraintFactory](https://github.com/mccalltd/AttributeRouting/blob/master/src/AttributeRouting/Framework/IRouteConstraintFactory.cs)? You can wire it up via config: ``` csharp routes.MapAttributeRoutes(config => { // ... config.RouteConstraintFactory = new CustomRouteConstraintFactory(); }); ```

Because Microsoft rolled their own implementation, inspired by this lib.

Query params don't work in web api web host, FYI. But if you're in self-host, should work (I think). The default and optional param together is nonsense, as you correctly...

No timeframe. You could just use [HttpRoute("url", HttpMethod.Patch)] for now. On Mar 19, 2013, at 7:03 PM, abpatel [email protected] wrote: Hi Tom, This is a coincidence. I was just searching...

Hmm. I think you are missing something. Can try a spike in the next day or two. Should be there, though. On Mar 19, 2013, at 8:31 PM, abpatel [email protected]...