Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

12
  • You are going to have to show the controller that is not working otherwise we'll be making assumptions as to why it doesn't work. Commented Apr 28, 2016 at 11:45
  • Ok I reread new issue and it could be an ordering issue with your routes. Framework uses first matched route. Try switching the order of the two convention based routes. Commented Apr 28, 2016 at 11:48
  • @Nkosi , I switched route order templates.When I try to access DamageEvent controller I get 405 error. Commented Apr 28, 2016 at 12:04
  • The new convention route you added. Do you need it for anything other than DamageEventController? If not then you can safely remove that route and keep your default as DamageEventController is fully using attribute routing. Commented Apr 28, 2016 at 12:10
  • @Nkosi You mean from actionAPI from WebApiConfig? Commented Apr 28, 2016 at 12:24