Unable to integrate Odata versioned apis with swagger for Asp.net web application

[vanikulkarniAtFIS]

We are using VersionedODataModelBuilder in Http application ( Asp.net web application)
Its does not have Owin startup hence we pass GlobalConfiguration.Configuration to VersionedODataModelBuilder constructor
Versiong of OData uri works fine as shown in the SwaggerODataWebApiSample
But while integrating this with swagger gives problems:

we create exploere as

var apiExplorer = configuration.AddODataApiExplorer(
options =>
{
options.GroupNameFormat = "'v'VVV";
options.SubstituteApiVersionInUrl = true;
});

The exception comes at
foreach (var group in apiExplorer.ApiDescriptions)
here apiExplorer.ApiDescriptions throws excpetion Invalid Operation exception
HttpConfiguration.Services.GetApiExplorer "This operation is not supported by 'HostedHttpRouteCollection'."
apiExplorer.ApiDescriptions: This operation is not supported by 'HostedHttpRouteCollection'.

The reasons could be : GlobalConfiguration.Configuration.Routes is a collection of HostedHttpRoutes
whereas in sample application we create new HttpConfigutation
Routes = {System.Web.Http.HttpRouteCollection}
vs
Routes = {System.Web.Http.WebHost.Routing.HostedHttpRouteCollection}
We also have normal ( non-odata) web apis as well

Swagger documentation is configured for them too.
Do you have any such example where odata versioning integrated with swagger and its not Owin

[commonsensesoftware]

I haven't seen this issue nor had anyone else report it. Using OWIN shouldn't matter, at least, not in this context. I mostly use OWIN for examples so that the Web API and ASP.NET Core examples have close parity.

I can't rule out a bug - yet. My cursory examination suggests that this might be an external. Are you by chance modifying the route collection in any way? Do you happen to have a repro handy? I can certainly create one, but working from something simple you already have is faster and an par with your expected setup.

[vanikulkarniAtFIS]

Chris,
Thanks for your quick reply.
At the moment I cannot upload the source code as its against security policy,
There no way to modify route collection as its read only property
What could be the external factors you think is affecting this?
We are using

config.Services.Replace(typeof(IApiExplorer), new IntegrationServicesApiExplorer());
IntegrationServicesApiExplorer is searching for controllers in the IntegrationServices folder.
My OData Controllers and normal web api controllers lie in the same folder
I don't think this should affect it.

I have attached sample code the comment below.
Please suggest some fix/ workaround for this.

[vanikulkarniAtFIS]

Swashbuckle.OData.Sample.zip

Please find attached sample code where the issue is reproduced
We are facing this issue

System.NotSupportedException was unhandled by user code
HResult=-2146233067
Message=This operation is not supported by 'HostedHttpRouteCollection'.
Source=System.Web.Http.WebHost
StackTrace:
at System.Web.Http.WebHost.Routing.HostedHttpRouteCollection.CopyTo(KeyValuePair2[] array, Int32 arrayIndex) at System.Web.Http.HttpRouteCollectionExtensions.GetRouteName(HttpRouteCollection routes, IHttpRoute route) at System.Web.Http.HttpConfigurationExtensions.GetODataRootContainer(HttpConfiguration configuration, IHttpRoute route) at Microsoft.Web.Http.Description.ODataApiExplorer.ExploreRouteControllers(IDictionary2 controllerMappings, IHttpRoute route, ApiVersion apiVersion)
at Microsoft.Web.Http.Description.VersionedApiExplorer.InitializeApiDescriptions()
at System.Lazy1.CreateValue() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Lazy1.get_Value()
at Microsoft.Web.Http.Description.VersionedApiExplorer.get_ApiDescriptions()
InnerException:

[vanikulkarniAtFIS]

Hi Chris, I have added sample application on #302 yesterday. Please have a look at it. The exact issue is reproduced in the sample app. This has become quite urgent for us as we want to roll out client side OData apis for version 1. Looking forward for your quick reply.

[vanikulkarniAtFIS]

Chris, Any updates on this? Did you get chance to debug sample application?

[commonsensesoftware]

Sorry for the delayed response, I've been really overloaded lately. Thanks for your patience. I tried downloading your sample application, but it seems it's no longer there. I don't think GitHub expires this content. Can you try adding it again?

I noticed you said you're using:

config.Services.Replace(typeof(IApiExplorer), new IntegrationServicesApiExplorer());

Is IntegrationServicesApiExplorer an extension of ODataApiExplorer? If it's not, then I expect this to fail. There is little-to-no support for OData and the IApiExplorer out-of-the-box. I provide a separate package and library to support that. It's normally registered and used as:

var apiExplorer = config.AddODataApiExplorer();

This ultimately calls config.Services.Replace(typeof(IApiExplorer), new ODataApiExplorer(config, options)). If you want to extend and provide your own customizations, that is a supported scenario. You'll just need to do the registration manually as you're currently doing. If you find a gap or limitation in customizing the current ODataApiExplorer implementation, I'm happy to discuss the changes needed to unblock you.

[vanikulkarniAtFIS]

Thanks for your reply. In tha sample application we are not replacing IApiExplorer. Attaching the zip file again. Let me know if you can see this

Swashbuckle.OData.Sample.zip

[commonsensesoftware]

I think I see the problem. You're replacing the IHttpControllerSelector, but I don't know why. That's likely going to break API versioning, the API Explorer, or both. It appears that you started trying to build your own API versioning library and then switched.

The IHttpControllerSelector is one of the core services that API versioning changes. You can see the implementation here. You can certainly extend and/or customize things, but if you go down that path, you will not want to use AddApiVersioning. Instead, you'll want to register the services manually. From a routing perspective, there is no difference to API versioning between OData and non-OData routes; that's why they don't have different configuration methods. The things that change for OData is versioning the EDM and adding version-aware OData route conventions.

I've provided a number of OData samples - with and without Swagger. I think you're facing issues from customizations that may no longer be needed (on your side). If there is some customization or configuration you need that isn't supported, I'm happy to help you sort that out. If there's gap in design, then I want to hear about that too.

Thanks

[commonsensesoftware]

Yureka! I see what the problem is. You are trying to follow and use code from the Swashbuckle + OData project. I just noticed something that caught my eye and made me double-check.

That project is completely different, unrelated, and not compatible with the API versioning libraries.

This is the first time I've seen this confusion, but I should probably mention something about that on the wiki. This project provides an implementation for IApiExplorer. It actually has no dependencies on Swashbuckle or Swagger in any way. Swashbuckle uses the IApiExplorer for the Web API implementation to support Swagger.

For an end-to-end working solution with API versioning, OData, and Swagger (a la Swashbuckle), please review the sample I provide. You should be able fork it and get it running for your project in no time.

I hope that helps. I'm happy to answer any other questions.