fix #6910

Co-authored-by: Maira Wenzel <mairaw@microsoft.com>
This commit is contained in:
Varorbc 2021-11-24 02:53:04 +08:00 коммит произвёл GitHub
Родитель d66a75e17f
Коммит ddfb3d38ad
Не найден ключ, соответствующий данной подписи
Идентификатор ключа GPG: 4AEE18F83AFDEB23
12 изменённых файлов: 40 добавлений и 40 удалений

2
.github/ISSUE_TEMPLATE/01_bug_report.md поставляемый
Просмотреть файл

@ -30,7 +30,7 @@ assignees: ''
### Regression?
<!--
* Did this work in a previous build or release of .NET Core, or from .NET Framework? If you can try a previous release or build to find out, that can help us narrow down the problem. If you don't know, that's OK.
* Did this work in a previous build or release of .NET, or from .NET Framework? If you can try a previous release or build to find out, that can help us narrow down the problem. If you don't know, that's OK.
-->
### Other information

Просмотреть файл

@ -4,4 +4,4 @@ See [Contributing](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md)
# Repos
See the [.NET Core Repos](Documentation/core-repos.md) to find a repo to contribute to.
See the [.NET Repos](Documentation/core-repos.md) to find a repo to contribute to.

Просмотреть файл

@ -1,6 +1,6 @@
# What you can expect from Maintainers
The .NET Core maintainer team aims to support a productive and safe working environment for everyone participating in .NET repositories. You can expect maintainers to do three things to that end: respect your contributions, make engagement efficient, and report potential .NET Foundation Code of Conduct violations.
The .NET maintainer team aims to support a productive and safe working environment for everyone participating in .NET repositories. You can expect maintainers to do three things to that end: respect your contributions, make engagement efficient, and report potential .NET Foundation Code of Conduct violations.
The following two lists summarize how maintainers will act. A more detailed description follows this summary.

Просмотреть файл

@ -1,22 +1,22 @@
# .NET repositories
.NET Core consists of many repositories. To file an issue, make a PR, or engage on specific topics, it's best to engage with developers working in the correct repo. A largely complete set of .NET Core and related repositories follows.
.NET consists of many repositories. To file an issue, make a PR, or engage on specific topics, it's best to engage with developers working in the correct repo. A largely complete set of .NET and related repositories follows.
## .NET Core
## .NET
|Repository |Description |
|--------------------------------------------------------------------|------------|
|[dotnet/core](https://github.com/dotnet/core) |.NET Core home repository|
|[dotnet/runtime](https://github.com/dotnet/runtime) |.NET Core runtime, runtime installers, application model, & Base Class Library (BCL)|
|[dotnet/core](https://github.com/dotnet/core) |.NET home repository|
|[dotnet/runtime](https://github.com/dotnet/runtime) |.NET runtime, runtime installers, application model, & Base Class Library (BCL)|
|[dotnet/docs](https://github.com/dotnet/docs) |.NET documentation|
|[dotnet/dotnet-api-docs](https://github.com/dotnet/dotnet-api-docs) |.NET API documentation|
|[dotnet/project-system](https://github.com/dotnet/project-system) |Visual Studio project system for C#, F#, & VB|
|[dotnet/sdk](https://github.com/dotnet/sdk) |.NET Core SDK (used by Visual Studio & .NET Core CLI)|
|[dotnet/installer](https://github.com/dotnet/installer) |.NET Core installer (produces zips, tarballs, and installers for the .NET SDK)
|[dotnet/sdk](https://github.com/dotnet/sdk) |.NET SDK (used by Visual Studio & .NET CLI)|
|[dotnet/installer](https://github.com/dotnet/installer) |.NET installer (produces zips, tarballs, and installers for the .NET SDK)
|[dotnet/extensions](https://github.com/dotnet/extensions) |.NET extension APIs (DI, logging, configuration, etc.)|
|[dotnet/dotnet-docker](https://github.com/dotnet/dotnet-docker) |.NET Core Docker images|
|[dotnet/dotnet-docker](https://github.com/dotnet/dotnet-docker) |.NET Docker images|
|[dotnet/templating](https://github.com/dotnet/templating) |Templating engine used by `dotnet new`|
|[dotnet/test-templates](https://github.com/dotnet/test-templates) |.NET Core unit testing project templates|
|[dotnet/test-templates](https://github.com/dotnet/test-templates) |.NET unit testing project templates|
|[dotnet/winforms](https://github.com/dotnet/winforms) |Windows Forms|
|[dotnet/wpf](https://github.com/dotnet/wpf) |Windows Presentation Foundation (WPF)|
|[dotnet/maui](https://github.com/dotnet/maui) |.NET Multi-platform App UI|

Просмотреть файл

@ -1,13 +1,13 @@
# Portable PDB #
.NET Core introduces a new symbol file (PDB) format - portable PDBs. Unlike traditional PDBs which are Windows-only, portable PDBs can be created and read on all platforms.
.NET introduces a new symbol file (PDB) format - portable PDBs. Unlike traditional PDBs which are Windows-only, portable PDBs can be created and read on all platforms.
## What is a PDB? ##
For anyone not familiar, a PDB file is an auxiliary file produced by a compiler to provide other tools, especially debuggers, information about what is in the main executable file and how it was produced. For example, a debugger reads a PDB to map foo.cs line 12 to the right executable location so that it can set a breakpoint.
The Windows PDB format has been around a long time now (~25 years), and it evolved from other native debugging symbol formats which were even older. It started out its life as a format for native (C/C++) programs. For the first release of the .NET Framework, the Windows PDB format was extended to support .NET.
## Why a new format? ##
While the Windows PDB format has worked okay over the years, with .NET Core the [Roslyn](https://github.com/dotnet/roslyn/wiki/Roslyn%20Overview) team decided it was time to go back to the drawing board and come up with a new format. A few of the reasons:
While the Windows PDB format has worked okay over the years, with .NET the [Roslyn](https://github.com/dotnet/roslyn/wiki/Roslyn%20Overview) team decided it was time to go back to the drawing board and come up with a new format. A few of the reasons:
* The Windows PDB format is complex, and not well documented. This complexity is important for some of the native code scenarios that the format was designed for, but it is unnecessary for the .NET scenarios. The portable format is [open source](https://github.com/dotnet/symreader-portable) and [documented](https://github.com/dotnet/runtime/blob/main/docs/design/specs/PortablePdb-Metadata.md).
* At the time the effort was begun there wasn't a cross-platform library that could read or write the original windows PDB format.

Просмотреть файл

@ -17,7 +17,7 @@ You need to join teams in two organizations. Click the two links:
After you join the teams:
* Users will be able to @mention you on [.NET Core Repos](https://github.com/dotnet/core/blob/main/Documentation/core-repos.md)
* Users will be able to @mention you on [.NET Repos](https://github.com/dotnet/core/blob/main/Documentation/core-repos.md)
* You will be able to access to private repos we maintain
* You will get write access to a subset of repos
@ -89,5 +89,5 @@ Service accounts should also be linked. For more details, see [Service accounts
## Guidelines
* [Contributing to .NET Core](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md)
* [Contributing to .NET](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md)
* [What you can expect from Maintainers](https://github.com/dotnet/core/blob/main/Documentation/contributing/maintainers.md)

Просмотреть файл

@ -1,8 +1,8 @@
# Official Microsoft Docs
Microsoft maintains official documentation for .NET, listed below. Both .NET Core and .NET Framework docs are relevant to .NET Core developers, both because many .NET Framework APIs are part of .NET Core (most relevant for .NET Core 2.0) but also because you can reference .NET Framework libraries with .NET Standard 2.0.
Microsoft maintains official documentation for .NET, listed below. Both .NET and .NET Framework docs are relevant to .NET developers, both because many .NET Framework APIs are part of .NET (most relevant for .NET Core 2.0) but also because you can reference .NET Framework libraries with .NET Standard 2.0.
## .NET Core
## .NET
- [Conceptual docs](https://docs.microsoft.com/dotnet/core/)
- [API docs](https://docs.microsoft.com/dotnet/api/)

Просмотреть файл

@ -1,7 +1,7 @@
.NET Core native prerequisites
.NET native prerequisites
==============================
* [Windows Prerequisites](https://docs.microsoft.com/dotnet/core/install/windows)
* [macOS Prerequisites](https://docs.microsoft.com/dotnet/core/install/macos)
* [Linux Prerequisites](https://docs.microsoft.com/dotnet/core/install/linux)
* [.NET Core Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md)
* [.NET Supported OS Lifecycle Policy](https://github.com/dotnet/core/blob/main/os-lifecycle-policy.md)

Просмотреть файл

@ -1,23 +1,23 @@
# .NET Core Home
# .NET Home
The dotnet/core repository is a good starting point for .NET Core.
The dotnet/core repository is a good starting point for .NET.
The latest major release is [.NET 6.0](release-notes/6.0/README.md). The latest patch updates are listed in [.NET Core release notes](release-notes/README.md).
The latest major release is [.NET 6.0](release-notes/6.0/README.md). The latest patch updates are listed in [.NET release notes](release-notes/README.md).
## .NET Core Releases
## .NET Releases
* [Download the latest .NET Core SDK](https://dotnet.microsoft.com/download/dotnet/6.0)
* [.NET Core releases](releases.md)
* [.NET Core daily builds](daily-builds.md)
* [Download the latest .NET SDK](https://dotnet.microsoft.com/download/dotnet/6.0)
* [.NET releases](releases.md)
* [.NET daily builds](daily-builds.md)
## Learn about .NET Core
## Learn about .NET
* [Learn about .NET Core](https://docs.microsoft.com/dotnet/core)
* [.NET Core Roadmap](https://github.com/dotnet/core/blob/main/roadmap.md)
* [Learn about .NET](https://docs.microsoft.com/dotnet/core)
* [.NET Roadmap](https://github.com/dotnet/core/blob/main/roadmap.md)
* [Learn about the .NET platform](https://docs.microsoft.com/dotnet/standard/)
* [.NET Core release notes](https://github.com/dotnet/core/blob/main/release-notes/README.md)
* [.NET Core Announcements](https://github.com/dotnet/announcements)
* [.NET Core blog](https://blogs.msdn.microsoft.com/dotnet/tag/net-core/)
* [.NET release notes](https://github.com/dotnet/core/blob/main/release-notes/README.md)
* [.NET Announcements](https://github.com/dotnet/announcements)
* [.NET blog](https://blogs.msdn.microsoft.com/dotnet/tag/net-core/)
## Getting help
@ -28,7 +28,7 @@ The latest major release is [.NET 6.0](release-notes/6.0/README.md). The latest
## How to Engage, Contribute and Provide Feedback
The .NET Core team encourages [contributions](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md), both issues and PRs. The first step is finding the [.NET Core repository](Documentation/core-repos.md) that you want to contribute to.
The .NET team encourages [contributions](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md), both issues and PRs. The first step is finding the [.NET repository](Documentation/core-repos.md) that you want to contribute to.
Check the [product roadmap](https://aka.ms/dotnet-product-roadmap) to see what the team is focusing on.
@ -39,11 +39,11 @@ Instances of abusive, harassing, or otherwise unacceptable behavior may be repor
## .NET Foundation
The .NET Core platform is part of the [.NET Foundation](https://www.dotnetfoundation.org).
The .NET platform is part of the [.NET Foundation](https://www.dotnetfoundation.org).
## Licenses
.NET Core repos typically use either the [MIT](LICENSE.TXT) or
.NET repos typically use either the [MIT](LICENSE.TXT) or
[Apache 2](https://www.apache.org/licenses/LICENSE-2.0) licenses for code.
Some projects license documentation and other forms of content under
[Creative Commons Attribution 4.0](https://creativecommons.org/licenses/by/4.0/).

Просмотреть файл

@ -2,7 +2,7 @@
## Supported Versions
The .NET Core and ASP.NET Core support policy, including supported versions can be found at the [.NET Core Support Policy Page](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
The .NET and ASP.NET Core support policy, including supported versions can be found at the [.NET Support Policy Page](https://dotnet.microsoft.com/platform/support/policy/dotnet-core).
## Reporting a Vulnerability
@ -10,6 +10,6 @@ Security issues and bugs should be reported privately to the Microsoft Security
You should receive a response within 24 hours. If for some reason you do not, please follow up via email to ensure we received your
original message. Further information, including the MSRC PGP key, can be found in the [MSRC Report an Issue FAQ](https://www.microsoft.com/msrc/faqs-report-an-issue).
Reports via MSRC may qualify for the .NET Core Bug Bounty. Details of the .NET Core Bug Bounty including terms and conditions are at [https://aka.ms/corebounty](https://aka.ms/corebounty).
Reports via MSRC may qualify for the .NET Bug Bounty. Details of the .NET Bug Bounty including terms and conditions are at [https://aka.ms/corebounty](https://aka.ms/corebounty).
Please do not open issues for anything you think might have a security implication.

Просмотреть файл

@ -22,4 +22,4 @@ Servicing branches are for new patch versions of .NET that have not yet been rel
|:------:|:------:|:------:|
|SDK|[.NET SDK 5.0.xxx](https://github.com/dotnet/installer/blob/main/README.md#installers-and-binaries)|[.NET Core SDK 3.1.xxx](https://github.com/dotnet/core-sdk/blob/main/README.md#installers-and-binaries)
|ASP.NET Core|[ASP.NET Core 5.0](https://github.com/dotnet/aspnetcore/blob/main/docs/DailyBuilds.md)|[ASP.NET Core 3.1](https://github.com/dotnet/aspnetcore/blob/main/docs/DailyBuilds.md)|
|Runtime|[.NET Core Runtime 5.0](https://github.com/dotnet/installer/blob/master/README.md#daily-builds)|[.NET Core Runtime 3.1](https://github.com/dotnet/core-setup/blob/master/README.md#daily-builds)
|Runtime|[.NET Runtime 5.0](https://github.com/dotnet/installer/blob/master/README.md#daily-builds)|[.NET Core Runtime 3.1](https://github.com/dotnet/core-setup/blob/master/README.md#daily-builds)

Просмотреть файл

@ -46,11 +46,11 @@ Here's what the script does.
You can use Snap is to install and try .NET Previews on [Linux distributions that support Snap](https://docs.snapcraft.io/installing-snapd/6735).
After configuring Snap on your system, run the following command to install the latest .NET Core SDK.
After configuring Snap on your system, run the following command to install the latest .NET SDK.
`sudo snap install dotnet-sdk --channel=6.0/beta --classic`
When .NET Core is installed using the Snap package, the default .NET Core command is `dotnet-sdk.dotnet`, as opposed to just `dotnet`. The benefit of the namespaced command is that it will not conflict with a globally installed .NET Core version you may have. This command can be aliased to `dotnet` with:
When .NET is installed using the Snap package, the default .NET command is `dotnet-sdk.dotnet`, as opposed to just `dotnet`. The benefit of the namespaced command is that it will not conflict with a globally installed .NET version you may have. This command can be aliased to `dotnet` with:
`sudo snap alias dotnet-sdk.dotnet dotnet`