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: README.md
+14-5Lines changed: 14 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ While it is possible to use the C# extension as a standalone extension, we highl
8
8
2. Open a folder/workspace that contains a C# project (.csproj) and a C# solution (.sln) and the extension will activate.
9
9
3. Whether you install C# Dev Kit or just the C# extension, the [.NET Runtime Installer Tool extension](https://marketplace.visualstudio.com/items?itemName=ms-dotnettools.vscode-dotnet-runtime) will be installed as a dependency.
10
10
11
-
Note: If working on a solution that requires versions prior to .NET 6 or non-solution based projects, install a Full Framework runtime and [MSBuild tooling](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022).
11
+
Note: If working on a solution that requires versions prior to .NET 6 or non-solution based projects, install a .NET Framework runtime and [MSBuild tooling](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022).
12
12
* Set omnisharp.useModernNet to false and set dotnet.server.useOmnisharp to true
13
13
* Uninstall or disable C# Dev Kit
14
14
* Windows: .NET Framework along with [MSBuild Tools](https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022)
@@ -29,11 +29,20 @@ For more information you can:
29
29
## How to use OmniSharp?
30
30
If you don’t want to take advantage of the great Language Server features, you can revert back to using OmniSharp by going to the Extension settings and setting `dotnet.server.useOmnisharp` to true. Next, uninstall or disable C# Dev Kit. Finally, restart VS Code for this to take effect.
31
31
32
-
33
32
## Found a Bug?
34
-
To file a new issue to include all the related config information directly from vscode by entering the command pallette with Ctrl+Shift+P (Cmd+Shift+P on macOS) and running CSharp: Report an issue command. This will open a browser window with all the necessary information related to the installed extensions, dotnet version, mono version, etc. Enter all the remaining information and hit submit.
35
-
Alternatively you could visit https://github.com/dotnet/vscode-csharp/issues and file a new one.
36
-
33
+
To file a new issue:
34
+
35
+
1. Go to “Settings” and search for Trace in the search bar.
36
+
2. From the drop-down, set Dotnet > Server to Trace. This will provide more output information for the developer team to diagnose the issue.
37
+
3. Reload the window by opening the Command Palette with Ctrl + Shift + P (Cmd + Shift + P on macOS), type "Reload Window," and press Enter.
38
+
4. Next, check the C# logs in the Output Window by opening it with Ctrl + Shift + U and selecting C# from the dropdown.
39
+
5. Select and copy all the text in the log, and then report the issue through VS Code.
40
+
6. Open the Command Palette with Ctrl + Shift + P (Cmd + Shift + P on macOS), type and select “CSharp: Report an issue”
41
+
7. This will open a window with all the necessary information related to the C# extension, dotnet version, mono version, etc.
42
+
8. Paste the previously copied log into the “Steps to Reproduce” field. Please also include a description of what you were doing/attempting to do at the time the problem occurred.
43
+
9. Click the “Preview on GitHub” button, and then file the issue.
44
+
45
+
Alternatively, you could visit https://github.com/dotnet/vscode-csharp/issues and file a new issue there.
0 commit comments