Sebastiaan Dammann
Sebastiaan Dammann
As per [vnext](https://github.com/Sebazzz/SDammann.WebApi.Versioning/tree/vnext) branch the `VersionedApiExplorer` needs reimplementing.
For now only major versions are supported but pull requests are welcome.
I agree, versioning should be explicit.
The reason those types are either private or internal is that primary means of extension is supposed to be through `IControllerVersionDetector` and friends. I realise that this does not fit...
What is the exact use case? You have explained the 'how' and the 'what' but I'm missing why. Don't understand me wrong here: I am only trying to understand why...
Sorry for the late response, but I had some thought over this to figure out a solution. This solution would be: - Possibility to handle an 'ControllerNotFound' event, let's say,...
Yes, I agree, paging would be useful and also a useful workaround until rendering performance is increased.
You're right. Throwing a custom exception, and then using an exception handler to rethrow it in the proper format is a good choice, of which I didn't think during development...
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. See the readme file...
I did notice that I can't always turn the AC back on when it is in cleaning mode, but I can do it through the Toshiba app.