116 votesjoshbooker supported this idea ·
Thank you for your feedback!
We would like to add more robust OData support. I am placing this item in “unplanned” to be used in future planning sessions.
Azure App Service Team
Update: I was able to get swagger to work, I think, but it wasn't pretty ( had to change my WebAPI routing prefixes and build my own version of System.Web.HTTP.OData).
Although the project did indeed publish to Azure successfully, I get errors on the API Definition blade in Azure portal. For more details, please see the following forums post:
After testing this, it is indeed the case that ODataController can't swagger. It appears to be a simple change needed in ODataController class.
Please reverse this change:
And or let us know how to override the following line:
[ApiExplorerSettings(IgnoreApi = true)]
Joshjoshbooker shared this idea ·
The RTM image should be available on the day of release - that was yesterday.