Error with versioning with attribute routing in ASP.NET WebAPI 2

Question

Found one example on the whole Internet of the following, and it was on StackOverflow, but there was no follow up whether it had been solved or not. This error happened after I implemented accept header versioning with attribute routing in a WebAPI 2 project.

Message: "An error has occurred." ExceptionMessage: "The given key was not present in the dictionary." ExceptionType: "System.Collections.Generic.KeyNotFoundException"

found here on stackoverflow:

How to get controller name when Web API versioning with routing attribues

Had the same problem. Restart of the Web Application in IIS solved this (especially after the update to WebApi 2.2 with inherit controllers) — Luuk
– Luuk, Commented Dec 29, 2014 at 15:52

Kiran · Accepted Answer · 2014-06-02 03:35:19Z

0

I am not sure how you implemented this as you have not shared any code, but you can take a look at the following sample demonstrating Web API's attribute routing and versioning through route constraints.

http://aspnet.codeplex.com/SourceControl/latest#Samples/WebApi/RoutingConstraintsSample/ReadMe.txt

The above sample looks for a custom header called api-version, but you can easily modify this to suit your scenario.

answered Jun 2, 2014 at 3:35

Kiran

58.1k16 gold badges179 silver badges163 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Rick Over a year ago

Not doing anything fancy. I will post the code a few minutes.

Collectives™ on Stack Overflow

Error with versioning with attribute routing in ASP.NET WebAPI 2

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related