New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[release/6.0] Add support for minimal APIs in ApiDescription.Server #44227
Conversation
Hi @captainsafia. If this is not a tell-mode PR, please make sure to follow the instructions laid out in the servicing process document. |
Hi @captainsafia. Please make sure you've updated the PR description to use the Shiproom Template. Also, make sure this PR is not marked as a draft and is ready-to-merge. To learn more about how to prepare a servicing PR click here. |
Suggest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Note branches are not currently open
Done!
Yep -- just getting it teed up since it came up recently. |
Description
This PR update the
dotnet getdocument
tool to react to changes in hosting that were shipped in .NET 6.The hosting changes were incongruent with the strategy that the
getdocument
tool used to extract the active ServiceProvider from the application assembly.This is a backport of a fix that was released in NET 7.0.
Closes #44215
Customer Impact
Without this change, OpenAPI document generation in the CLI and client generation in Visual Studio would fail to produce the necessary schemas and code for minimal API endpoints in user applications.
Regression?
Risk
Low because:
getdocument
toolVerification
Packaging changes reviewed?