OpenApi support - Microsoft.AspNetCore.OpenApi namespaces vs Microsoft.AspNetCore.Mvc namespaces ...

[bdcoder2]

This is more just out of curiosity, but I build a lot of minimal API's / services that do NOT use MVC or Blazor and have noticed that when using a call such as:

Microsoft.AspNetCore.Builder.WebApplication.CreateBuilder()

The following MVC services are automatically injected:

Microsoft.AspNetCore.Mvc.ApiExplorer.IApiDescriptionGroupCollectionProvider
Microsoft.AspNetCore.Mvc.ApiExplorer.IApiDescriptionProvider
Microsoft.AspNetCore.Mvc.Infrastructure.IActionDescriptorCollectionProvider

Yes, I realize there is a Microsoft.AspNetCore.Builder.WebApplication.CreateEmptyBuilder method which may not load the above services, but it just seems odd that these services are included, when not really required - or are they? ...

If I create an OpenAPI document for an API, it turns out the Microsoft.AspNetCore.OpenApi.OpenApiOptions.ShouldInclude method makes use of: Microsoft.AspNetCore.Mvc.ApiExplorer.ApiDescription, which again, seems odd (to me). I would have expected that the ApiDescription should be a part of the Microsoft.AspNetCore.OpenApi namespace instead of an MVC namespace.

Just wondering if all things OpenApi should "live" under the Microsoft.AspNetCore.OpenApi namespace rather than the some living under the Microsoft.AspNetCore.Mvc. namespace.

Would also be great if the documentation for all the various Microsoft.AspNetCore.Builder.WebApplication.Create*Builder() methods included an explicit list of the services that are injected and the rationale for each.

Thanks in advance.

[martincostello]

The "Mvc" part of the naming is just a historical artefact at this point. These types were part of MVC when the other things such as Blazor or Minimal APIs didn't exist, and were moved to different assemblies to remove the actual dependency on MVC for such types of projects. Changing their namespace would have been a breaking change though, so they were left named as they were originally created.

[bdcoder2]

Thanks Martin for your quick reply.

I thought that may have been the case. Perhaps down the road(map), all OpenApi "stuff" will be found under a common Microsoft.AspNetCore.OpenApi, which would really make more sense as OpenApi is a standard that has no real relationship with MVC.

Cheers.