You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: CONTRIBUTING.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -2,6 +2,6 @@
2
2
3
3
See [Contributing](https://github.com/dotnet/runtime/blob/main/CONTRIBUTING.md) for information about coding styles, source structure, making pull requests, and more.
4
4
5
-
# Repositories
5
+
##Repositories
6
6
7
7
See the [.NET Repos](Documentation/core-repos.md) to find a repo to contribute to.
Copy file name to clipboardexpand all lines: Documentation/contributing/maintainers.md
+5-3
Original file line number
Diff line number
Diff line change
@@ -4,13 +4,15 @@ The .NET maintainer team aims to support a productive and safe working environme
4
4
5
5
The following two lists summarize how maintainers will act. A more detailed description follows this summary.
6
6
7
-
**Maintainers will**
7
+
Maintainers will:
8
+
8
9
- Encourage your contributions and participation and provide clear and direct feedback, including when your contributions are not accepted.
9
10
- Close issues and PRs as a means of making repos more efficient to use for everyone. They can be re-opened, as needed.
10
11
- Edit comments for formatting [if and only if (iff)](https://en.wikipedia.org/wiki/If_and_only_if) the edit adds substantially to the readability or usability of the comment. No changes will be made to spelling, wording, meaning, or emphasis.
11
12
- Report abusive behavior to the [Code of Conduct review group](mailto:[email protected]).
12
13
13
-
**Maintainers won't**
14
+
Maintainers won't:
15
+
14
16
- Edit contributor comments as a general rule. GitHub provides [edit history](https://blog.github.com/changelog/2018-05-24-comment-edit-history/) which makes editing more acceptable as there is a way to see an audit log. However, contributors might still be surprised when they see statements or phrases under their name that they don't recall making. Transparency is a cornerstone of effective discourse and its absence undermines trust. And a change log doesn't fully eliminate these concerns.
15
17
16
18
## Respect your Contributions
@@ -27,7 +29,7 @@ Maintainers will take actions to make repo engagement more efficient for everyon
27
29
28
30
Maintainers may edit PR and issue titles to improve readability and/or accuracy. GitHub provides history for title changes.
29
31
30
-
Maintainers may edit your comments if and only if the edit adds substantially to the readability or usability of the comment and doesn't change the content. The maintainer will add a short descriptive note with their @handle to explain their change at the end of your comment (for example: "_Edited by @richlander -- added call-stack formatting_").
32
+
Maintainers may edit your comments if and only if the edit adds substantially to the readability or usability of the comment and doesn't change the content. The maintainer will add a short descriptive note with their @handle to explain their change at the end of your comment (for example: "_Edited by @richlander -- added call-stack formatting_").
31
33
32
34
Maintainers may make the following changes to contributor comments:
|[dotnet/installer](https://github.com/dotnet/installer) |[🔗](https://github.com/dotnet/installer/issues) | |.NET installer (produces zips, tarballs, and installers for the .NET SDK)
51
+
|[dotnet/installer](https://github.com/dotnet/installer)|[🔗](https://github.com/dotnet/installer/issues)||.NET installer (produces zips, tarballs, and installers for the .NET SDK)|
|[dotnet/test-templates](https://github.com/dotnet/test-templates)|[🔗](https://github.com/dotnet/test-templates/issues)||.NET unit testing project templates|
59
59
|[dotnet/vscode-csharp](https://github.com/dotnet/vscode-csharp)|[🔗](https://github.com/dotnet/vscode-csharp/issues)|[🔗](https://github.com/dotnet/vscode-csharp/discussions)|C# support for VS Code|
Copy file name to clipboardexpand all lines: Documentation/ilcRepro.md
+91-86
Original file line number
Diff line number
Diff line change
@@ -2,15 +2,12 @@
2
2
3
3
It looks like you probably hit a bug in .NET Native.
4
4
You can help make .NET better by sending a bug report.
5
-
However, take a look at the [Known Issues](#known-issues) section below
6
-
before sending a bug report. There may already be a
7
-
workaround for your issue.
8
5
9
6
## Creating and Sending a .NET Native repro
10
7
11
8
1. Add `<NetNativeReproPath>C:\myReproDirectory</NetNativeReproPath>` to the primary PropertyGroup in your project file, the file ending in csproj, vsproj, vcxproj, or jsproj. You can set `C:\myReproDirectory` to any directory that exists. [Examples are below.](#examples)
12
9
2. Rebuild your app. You will find ilcRepro.zip in the repro directory you specified above.
13
-
3. Put ilcRepro.zip on your OneDrive, Dropbox, or another storage provider. Send a link to ilcRepro.zip and a description of your issue to [email protected].
10
+
3. Put ilcRepro.zip on your OneDrive, Dropbox, or another storage provider. Send a link to ilcRepro.zip and a description of your issue to <[email protected]>.
14
11
4. Remove `<NetNativeReproPath>` from your project file.
15
12
16
13
## Compilation Failure in Store
@@ -19,102 +16,110 @@ UWP apps containing managed code are compiled in Store using the .NET Native Too
19
16
20
17
`This submission failed due to compilation error {0}. More information about this error can be found here.`
21
18
22
-
In such a case, please ensure that you were able to build your application in Release mode successfully at the time you submitted it to Store. If it did, please send the error number you got in the message above and email [email protected].
19
+
In such a case, please ensure that you were able to build your application in Release mode successfully at the time you submitted it to Store. If it did, please send the error number you got in the message above and email <[email protected]>.
23
20
24
-
For help with any other issues, please share their details at https://connect.microsoft.com/visualstudio/
21
+
For help with any other issues, please share their details at <https://connect.microsoft.com/visualstudio/>
25
22
26
23
## Examples
27
24
28
25
Below are examples of where to add the `<NetNativeReproPath>` tag.
Copy file name to clipboardexpand all lines: Documentation/microsoft-team.md
-1
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,6 @@ Register at least two of the following two-factor authentication methods:
19
19
*[Hardware security key(s)](https://docs.github.com/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-security-key) (also see [yubikey](https://www.yubico.com/works-with-yubikey/catalog/github/))
20
20
*[TOTP with an Authenticator app](https://docs.github.com/authentication/securing-your-account-with-two-factor-authentication-2fa/configuring-two-factor-authentication#configuring-two-factor-authentication-using-a-totp-mobile-app) (like [Microsoft Authenticator](https://support.microsoft.com/account-billing/download-and-install-the-microsoft-authenticator-app-351498fc-850a-45da-b7b6-27e523b8702a))
21
21
22
-
23
22
Additional guidance:
24
23
25
24
* Do not use [SMS](https://en.wikipedia.org/wiki/SIM_swap_scam) for 2FA or as a recovery fallback (disable those options).
0 commit comments