Skip to content

Commit 65e5e08

Browse files
authored
Add instructions for creating private feedback (#8732)
2 parents 29c1583 + a9a1b2d commit 65e5e08

File tree

2 files changed

+12
-2
lines changed

2 files changed

+12
-2
lines changed

SUPPORT.md

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ If you encounter issues with document classification (e.g., incorrect syntax hig
107107
For issues with diagnostics, please provide values of the background analysis scope options, `dotnet.backgroundAnalysis.analyzerDiagnosticsScope` and `dotnet.backgroundAnalysis.compilerDiagnosticsScope`
108108
![background analysis settings](./docs/images/background_analysis.png)
109109

110-
#### Language server crashing
110+
### Language server crashing
111111

112112
If the language server crashes, general logs are often helpful for diagnosing the issue. However, in some cases, logs alone may not provide enough information and we may need a crash dump. Follow these steps to collect a crash dump:
113113
- Set the `dotnet.server.crashDumpPath` setting in VSCode to a user-writable folder where crash dumps can be saved.
@@ -117,7 +117,7 @@ If the language server crashes, general logs are often helpful for diagnosing th
117117
> [!WARNING]
118118
> The dump can contain detailed information on the project - generally we will provide an email so that it can be shared privately
119119
120-
#### Recording a language server trace
120+
### Recording a language server trace
121121

122122
When investigating performance issues, we may request a performance trace of the language server to diagnose what is causing the problem. These are typically taken via [dotnet-trace](https://learn.microsoft.com/en-us/dotnet/core/diagnostics/dotnet-trace) (a cross platform tool to collect performance traces of .NET processes)
123123

@@ -132,6 +132,16 @@ The C# extension has a built in command, `csharp.recordLanguageServerTrace` to h
132132
![alt text](docs/images/recordTraceTerminal.png)
133133
5. Share the trace. Note that the trace may contain PII, so generally we will provide an email or other confidential way to share the trace with us.
134134

135+
### Sharing information privately
136+
Detailed logs, dumps, traces, and other information can sometimes contain private information that you do not wish to share publicly. Instead, you can utilize the Developer Community page to share these privately to Microsoft.
137+
138+
1. Go to https://developercommunity.visualstudio.com/dotnet/report
139+
2. Fill in the issue title, reference the GitHub issue in the description, and upload the attachments
140+
![developer community feedback page](docs/images/developer_community_feedback.png)
141+
3. Once created, a comment on the GitHub issue a link to the new Developer Community ticket.
142+
143+
144+
135145
## Microsoft Support Policy
136146

137147
Support for this project is limited to the resources listed above.
124 KB
Loading

0 commit comments

Comments
 (0)