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
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -120,9 +120,9 @@ If the language server crashes, general logs are often helpful for diagnosing th
120
120
121
121
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)
122
122
123
-
The C# extension has a built in command, `csharp.recordTrace` to help with trace collection. This command will install `dotnet-trace` as a global tool and invoke it against the language server.
123
+
The C# extension has a built in command, `csharp.recordLanguageServerTrace` to help with trace collection. This command will install `dotnet-trace` as a global tool and invoke it against the language server.
124
124
125
-
1. Invoke the `csharp.recordTrace` command
125
+
1. Invoke the record language server trace command
126
126

127
127
2. Select the folder to save the trace.
128
128
3. Accept the default trace arguments, or change them if requested
0 commit comments