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: SUPPORT.md
+12-2Lines changed: 12 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -107,7 +107,7 @@ If you encounter issues with document classification (e.g., incorrect syntax hig
107
107
For issues with diagnostics, please provide values of the background analysis scope options, `dotnet.backgroundAnalysis.analyzerDiagnosticsScope` and `dotnet.backgroundAnalysis.compilerDiagnosticsScope`
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:
113
113
- 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
117
117
> [!WARNING]
118
118
> The dump can contain detailed information on the project - generally we will provide an email so that it can be shared privately
119
119
120
-
####Recording a language server trace
120
+
### Recording a language server trace
121
121
122
122
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)
123
123
@@ -132,6 +132,16 @@ The C# extension has a built in command, `csharp.recordLanguageServerTrace` to h
132
132

133
133
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.
134
134
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
+

141
+
3. Once created, a comment on the GitHub issue a link to the new Developer Community ticket.
142
+
143
+
144
+
135
145
## Microsoft Support Policy
136
146
137
147
Support for this project is limited to the resources listed above.
0 commit comments