-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
C# Dev kit completely broken. Nothing works. #799
Comments
@wgrs Is it possible for you to provide more information about your workspace that you have open? What types of projects (looks like maybe Unity?), what, if any, log messages are emitted in the output window for "C#" and "C# Dev Kit" categories? This would better help us make this actionable. |
This is completely standard .net 8 webapi on Ubuntu 23.04. Its been broken for months. I have reinstalled everything even the OS. I opened other tickets on the vscode issues page giving the reason I though the cause was. That ticker was closed. Since then others have added the errors too. I was amazed it was just closed and no action taken. |
Yep that's not expected and not common. Can you share the output log stream if anything there? |
How do I get the output logs? |
Ok, for starters, I added a standard xunit test project and ran dotnet test.
The nugets for dotnet new xunit are very old so I updated them to the latest versions but the same error persists. |
Thanks Greg. You mentioned you ran Can you run |
Host: .NET SDKs installed: .NET runtimes installed: Other architectures found: Environment variables: global.json file: Learn more: |
Ok thanks. Was there any output in the C#/C# Dev Kit output logs? |
I reinstalled the Dev kit again. I had to uninstall it earlier and over the previous weeks because it was breaking refactoring, intellisense etc. As things would have it, go to definition is now working, intellisense seems to be working as well. No errors shown in workspace. All the dotnet commands work as expected. But I need to get tests working now. The Solution explorer is fine, although I have had to delete a mysterious sln object that randomly gets dropped into one of my projects. That would obviously cause issues but as of yesterday, even after I removed the rogue sln, intellisense, refactoring and testing were broken. |
Ok, correct it is not anything to do with VSCode or extensions, this is the runtime. /cc @AbhitejJohn @peterwald any ideas? At this point we should move this to dotnet/sdk? |
Appreciate the clarity and the help - so much better than just having the ticket closed which was happening on the vscode issue page. |
Sorry about that Greg...lots of teams, different processes :-( -- let's help to see if we can get your tests sorted. Will need Peter/Abhitej to chime in here. Could be an SDK issue -- I'm spinning up a linux machine now to see if I can replicate. |
So, back to broken again. Intellisense gone, goto definition gone, refactoring gone: dotnet build still working - no errors. Here is the output from C# Dev Kit Starting Spawn .NET server...
|
Ugh...okay, @arkalyanms seeing this on linux here -- is this a DOTNET_ROOT issue? @wgrs FYI the extension requires .NET 7 presently so it gets installed for you during activation if not found as a dependency...but may be messing with paths on Linux here. |
Not sure if this helps but there were major path issues when installing the SDK depending on the package manager used and whether installs were done using the Microsoft feeds or apt or snap |
It helps in validating exactly what I'm experiencing now as well. ;-) |
That's right. We have not seen this before. Taking a look. I'll reach out to you @timheuer in case you managed a repro we can use as well. |
Hello guys! I'm having the same issue, but I'm working on WSL.
Here are the dotnet --info output
As I'm on windows, though, I have the possibility to open the project outside WSL, and when I do that, something different happens: a popup appears asking me which solution I want to use for intellissense (as I have two in this folder). This popup doesn't appear when I'm on WSL, and I suspect this is the origin of the issue, because after I selected the solution, intelissense started to work. Also, the command .NET Open Solution successfully detects the existing solution when I'm opening the copy outside WSL, but it does not in the copy inside. So... maybe this is a sln detection problem with vscode running on linux? Edit: The .netstandard project only have one solution, and it's working. And I also had some random sln files dropping on my folder when I open it with WSL Edit2: I've just realized the I was opening the .netstandard project outside WSL, when I opened it on WSL, it had the same problem as the other one |
I ran dotnet --list-sdks which should show a list of all installed sdks - its only shows 8.0.100 |
@wgrs : I've not had much luck getting the dotnet test issue reproing on my end. Do you mind running |
|
Yes. The Dev Kit cripples everything so I uninstall it when working. With just the C# extension, there is basic intellisense and goto definition. I am working on Azure Function apps, WebApi and Blazor. |
Thank you @wgrs ! And just to clarify, do you keep the C# extension, and that works well? And if so, are you on the latest version of the C# extension? |
I am on the latest of everything. I can't say the C# extension is working. I can say that when I uninstall the Dev Kit, I have basic functionality such as code coloring (theme) working, goto def, basic intellisense. If those features are controlled by C# ext, then yes. Basic functionality works. Refactoring doesn't work in all cases. |
there are many different issues mixed in this thread. I guess issues related to the text window has been resolved. And multiple solution issue was raised in a different threads. Going back to the root of this thread, it is the intelli-sense doesn't work when both CD and C# extension are enabled. Recently, both extensions were updated to NET 8 runtime, and just want to check whether it changed anything? |
This issue has been automatically closed due to inactivity from original bug filer and having the 'needs-more-info' label for more than 14 days. If the issue still persists, please reopen the issue with the requested information. |
😂 Definitely not completed |
FWIW, the github action was fixed today morning via 3d246b5 |
@wgrs - can you confirm if the C# dev kit extension with the update for .NET 8 core is working as expected? Or are you still experiencing issues? |
Trying to dev with C# |
After different tryouts to make things work, it seems to work properly in VScode Insider* after an update but refuses to work in VScode (v. 1.88.1). |
I wrote it above already and hope people read this. It is very essential to have a correct .sln file, which is compatible with Visual Studio. MS is trying to close the gap between VS Code and Visual Studio so developers using these tools should not have compatibility issues. |
This is not the cause of my issue with the dev kit. In any event, VSCode should throw an exception if the sln file is incompatible with its requirement. |
@tmeschter, the 'needs-more-info' label has been removed upon receiving further response from the original bug filer. |
I have upgraded to Ubuntu 24.04. As this is still in Beta for a few more days, I can not yet confirm if the dev kit is working. I can confirm that docker is now broken but that is a separate issue. I will report back once 24.04 comes out of Beta. |
Not in my case. I just discovered it was the real cause. No warning at all. VS Code adds a sln file but an incorrect one, not reflecting the solution. After running VS on windows on the solution and fixing the sln file, going back to VS Code it fixed my intellisense. |
Thanks keep us posted. |
@egbertn Can you provide a copy of the sln file that was incorrect (and the fixed one as well please) if possible or repro steps for how you arrived at the incorrect solution file. Was the incorrect sln file generated in Windows OS or another? |
I was relating my experience after the dev extension and VS Code got upgrades some months ago. Thanks |
Ran a few .net project types on a clean Ubuntu 24.04. All looks good so far with the Dev kit. |
Removing high-priority based on recent update.
|
@wgrs Given that things are working for you now are you OK with us closing this issue? |
Yes thank you |
I tried it too and it is better. But I found now an issue with German Umlauts. If I name a component Measure.razor and use it in another component it will recognise it. But if I rename it to Maß.razor it does not find that component anymore. |
@MarkusRodler Opened new issue for the German Umlauts (#1096). Closing this one. |
Type: Bug
Refactoring completely broken along with intellisense. Testing doesnt work. In fact Im not sure anything is actually working on this ext. Wasted hours reinstalling countless times.
This extension is completely useless. This was supposed to fix all the omniCode stuff but its even worse than that tool. Its crippling vscode. Its a now a constant battle doing even basic things in vscode.
Zero refactoring, zero intellisense and zero testing.
Extension version: 1.1.16
VS Code version: Code 1.85.0 (af28b32d7e553898b2a91af498b1fb666fdebe0c, 2023-12-06T22:27:05.695Z)
OS version: Linux x64 6.5.0-14-generic snap
Modes:
System Info
canvas_oop_rasterization: disabled_off
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: disabled_software
multiple_raster_threads: enabled_on
opengl: disabled_off
rasterization: disabled_software
raw_draw: disabled_off_ok
video_decode: disabled_software
video_encode: disabled_software
vulkan: disabled_off
webgl: unavailable_software
webgl2: unavailable_software
webgpu: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: