Sebastiaan Dammann
Sebastiaan Dammann
Yes, attribute routing was not in any sense tested and thus supported. With your permission, I'd like to merge your code in the library. --- Van: Richard Pickettmailto:[email protected] Verzonden: 4-3-2015...
Currently not working on it, sorry.
I'm going to implement the proposal mentioned in #42. This would allow you to do this by implementing your own exception handler to handle such exceptions yourself.
In beta3, just pushed to nuget.org, you may either implement your own [global exception filter](http://www.asp.net/web-api/overview/error-handling/web-api-global-error-handling) or inherit from `DefaultVersioningExceptionHandler` and register `IVersioningExceptionHandler` with your DI container.
As per [vnext](https://github.com/Sebazzz/SDammann.WebApi.Versioning/tree/vnext) branch the `VersionedApiExplorer` needs reimplementing.
Wouldn't just ordering the `IEnumerable` passed to `AcceptHeaderVersionedControllerSelectorBase .GetVersionFromHeader` resolve that problem? ASP.NET is going to pick the MIME-type with the highest `q` for serializing the method body, and the...
Temporary workaround: Use the [WebApi.DocumentationController](https://nuget.org/packages/WebApi.DocumentationController/) library and register the shipped `XmlCommentDocumentationProvider`.
This broke as of the upgrade to Web Api 5.
As per [vnext](https://github.com/Sebazzz/SDammann.WebApi.Versioning/tree/vnext) branch the `VersionedApiExplorer` needs reimplementing. This issue will need to be taken into account.
I will look into it.