We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
https://docs.microsoft.com/en-ca/aspnet/core/tutorials/web-api-help-pages-using-swagger?view=aspnetcore-2.1 covers the current state of client code generation in ASP.NET Core web sites. However, we're working to give customers simple ways to annotate their project files for automated code generation during every build (as source API descriptions change) and that should also be documented.
Note tooling for the new experience isn't going to happen immediately. The initial documentation should focus on manual edits to .csproj files.
Does not cover work described in aspnet/Mvc#4947 and its sub-issues.
@glennc
The text was updated successfully, but these errors were encountered:
Copied to #8462
Sorry, something went wrong.
No branches or pull requests
General
https://docs.microsoft.com/en-ca/aspnet/core/tutorials/web-api-help-pages-using-swagger?view=aspnetcore-2.1 covers the current state of client code generation in ASP.NET Core web sites. However, we're working to give customers simple ways to annotate their project files for automated code generation during every build (as source API descriptions change) and that should also be documented.
Note tooling for the new experience isn't going to happen immediately. The initial documentation should focus on manual edits to .csproj files.
Issues with Existing Topics
Does not cover work described in aspnet/Mvc#4947 and its sub-issues.
CC
@glennc
The text was updated successfully, but these errors were encountered: