agilenut

@commonsensesoftware - Here is the [repro](https://github.com/agilenut/api-versioning-defaultresponsetype). Let me know if you have any questions.

@commonsensesoftware - I'd be willing to put up a PR but I haven't found exactly what is making the new version behave differently than the old version. If you had...

> It's unclear to me if that is the default behavior (which it seems to be) or if you have some customization that does the right thing. Yes. The initial...

I think I'm experiencing a similar issue. However, I'm not using minimal APIs. I'm still using controllers and a startup.cs (because I need to use it in my SwaggerHostFactory). In...

@Mhirji, thanks for the confirmation. If I move `app.UseSwaggerUI` to the last step in Startup.cs, it does work. However, that means that swagger UI is after `app.UseAuthorization` which means my...

@commonsensesoftware , I think the issue is that `app.UseAuthorization` must happen before `app.UseEndpoints`. And, `app.UseEndpoints` must happen before `app.UseSwaggerUI`. By the transitive property, that means `app.UseAuthorization` must happen before `app.UseSwaggerUI`....

True, the original question was for Minimal APIs. It just sounded to me like it might be because of the same underlying changes. If you'd like for me to open...

Thanks @commonsensesoftware. I've tested this with the latest version of `DefaultApiVersionDescriptionProvider` and I can confirm that it is now working! It works with both the "Old Style" in the examples...

I can confirm Preview 3 has fixed the issue I had related to this thread.

Our team has moved to the new version. Working well so far!