de099b775c
* Add breaking changes docs Fixes #33996 Add the configuration and TOC changes for publishing the breaking changes articles to the razor compiler. * Remove non-functioning attributes The file based meta data isn't working with this folder layout. So, add the metadata to the files directly See dotnet/razor#11199 |
||
---|---|---|
.github | ||
.vscode | ||
aspnetcore | ||
.editorconfig | ||
.gitattributes | ||
.gitignore | ||
.markdownlint.json | ||
.openpublishing.build.ps1 | ||
.openpublishing.publish.config.json | ||
.openpublishing.redirection.json | ||
.repoman.yml | ||
.whatsnew.json | ||
CODE_OF_CONDUCT.md | ||
CONTRIBUTING.md | ||
LICENSE | ||
LICENSE-CODE | ||
README.md | ||
ThirdPartyNotices | ||
cspell.json | ||
quest-config.json |
README.md
ASP.NET Core Docs
This repository contains the ASP.NET Core documentation. See the Contributing Guide and the issues list if you would like to help.
To provide comments and suggestions on learn.microsoft.com site functionality, open an issue in the MicrosoftDocs/feedback
GitHub repository.
ASP.NET 4.x documentation changes are made in the dotnet/AspNetDocs
GitHub repository.
How to open an issue
If the issue is with an ASP.NET Core document:
- Do not open a blank issue.
- Open the issue using the Open a documentation issue link and feedback form at the bottom of the article.
Using the Open a documentation issue link and form to open an issue adds article metadata for tracking, which indicates the article that you're commenting on and automatically pings the author for a faster response.
If the issue is:
- A simple typo or similar correction, you can submit a PR. See the contributor guide for instructions.
- A general support question, consider asking on a support forum site:
- A site design concern, create an issue at MicrosoftDocs/Feedback.
- A problem completing a tutorial, compare your code with the completed sample.
- A duplicate of an open or closed issue, leave a comment on that issue.