ApiExplorer ApiDescription error: The invoked member is not supported before the type is created.

[dmore234]

Using WebApi and oData v4. Getting exception in MultipleVersion block for EF models having navigation property. Do I have add IncludeNavigationPropery in Swagger Config file or exclude controllers having navigation property? Please advise!

The invoked member is not supported before the type is created.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.NotSupportedException: The invoked member is not supported before the type is created.

foreach (var group in apiExplorer.ApiDescriptions)....................Line 152:

[commonsensesoftware]

Which version of the libraries are you using? Are you using the current versions? There was an issue related to this area that has since been fixed, but there still might be a missing edge case.

Do you have a simple repro or configuration you can share. It's difficult to setup the conditions you're seeing otherwise. Thanks.

[dmore234]

Swashbuckle oData 3.5.0. Rest latest version.

[dmore234]

I have multiple oData controllers, is there a way to hide/not display certain controllers in Swagger UI?

I tried class level attribute [ApiExplorerSettings(IgnoreApi=true)] but it not working.

Thanks for your help!

[commonsensesoftware]

Oh … I think I see. Are you using the Swashbuckle.OData? If so, that's the culprit. It changes things that break API versioning. Fear not though. There's a solution and you don't need that package at all.

I strong recommend you have a deep look at the Web API OData Swagger sample project. It will show you all the packages and setup you need to get OData and Swagger working together.

API Versioning provides an extension to the API Explorer API. One of its possible uses for Swagger generation. As a result, you don't need a special variant of Swashbuckle or other Swagger generators like NSwag that use this information. You need API Versioning and plain 'ol Swashbuckle.

In your case, you packages should include:

• API Versioning for OData on Web API
• API Versioning API Explorer for OData on Web API
• Swashbuckle

Again - the working example will demonstrate everything work end-to-end. Give that a whirl and let me know if you have more questions.

I may need to put something on the wiki as the incompatibility with Swashbuckle.OData has come up a few times.

[dmore234]

In mentioned sample project ( .../aspnet-api-versioning-master\samples\webapi\SwaggerODataWebApiSample\Models) model Order & Person does NOT have Navigation Property.

ApiVersioning is working w/o Navigation property. I am getting error w NP.

[commonsensesoftware]

Navigation properties should be supported. I'll investigate further. If you have a repro or an example to share that really helps speed things up so that I can run through your exact scenario.

[dmore234]

I used the sample code from sample you mentioned in recent past ( .../aspnet-api-versioning-master\samples\webapi\SwaggerODataWebApiSample\Models) model Order & Person In this sample project can you add NP in Order / Person and see if multiple versioning is working or not. Steps are: 1) Use models with NP 2) Add [Apiversion("1.0")] and 2.0 in two controllers 3) Use c.MultipleVersion code in Startup.cs ....v{apiversion} Expectation is there should be 2 v1 & v2 in dropdown. All odata query should work like $select, $top $ expand.... Hope this will help! Thanks! Dilip More Thanks for our help! Dilip More Sent from Outlook<http://aka.ms/weboutlook>

…

________________________________ From: Chris Martinez <notifications@github.com> Sent: Tuesday, February 26, 2019 11:20 AM To: Microsoft/aspnet-api-versioning Cc: dmore234; Author Subject: Re: [Microsoft/aspnet-api-versioning] ApiExplorer ApiDescription error: The invoked member is not supported before the type is created. (#463) Navigation properties should be supported. I'll investigate further. If you have a repro or an example to share that really helps speed things up so that I can run through your exact scenario. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub<#463 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/Atrn1I_RbKXFJSYrC0aYl1cdGTAk1QY6ks5vRV7JgaJpZM4bNu4D>.