Language Server stops working about vscode-csharp HOT 7 CLOSED

@nelson-m-ferreira-sibs since you're using C# devkit .NET: Restart Language Server won't work (there is a known bug with that). However I would expect Reload window to function exactly the same as closing / re-opening.

Nothing looks like its going incredibly wrong from the logs. I do see that the language server restarted, which as above has a bug which will cause the language server to lose the project information, so definitely try reloading the window.

A couple of other questions

1. To confirm, you're losing colorization / completion suggestions in both .cs and .xaml files? If you can share a screenshot of the incorrect behavior that might help.
2. Is there any specific kind of change that triggers the behavior? For example does it always happen after making a change to a .csproj?
3. Are there any other popup warnings saying anything went wrong?

from vscode-csharp.

I was in the middle of writing a long comment with me having this issue as well. Meanwhile I left vscode running in the background - the state was as described in this issue - no colorization / completion suggestions. The logs indicated that everything was loaded and running, no errors or anything indicating something was wrong (even though the case was clearly the opposite).

Right before I hit send, I went back to vscode to confirm. And voilà, suddenly intellisense had kicked in. Not sure what the take from this should be, but maybe there is missing an indicator that things are still loading?

from vscode-csharp.

Hi @dibarbet

Yesterday after posting the issue I've updated the .NET MAUI VS Code extension to the v1.1.14 (pre-release) version and I haven't used it enough today to provide a complete feedback, but I'll try to answer as far as I'm able to:

1. Yes, I'm losing both colorization and completion in both .cs and .xaml files, having only the basic auto-completion present on VS Code (the one that has the "abc" icon);
2. I'm still unable to provide a single point that causes this error to occur but I can guarantee that no .csproj changes are being made (both manually or automatically, since I'm only editing the current files and not adding/removing/renaming files). One thing I haven't mentioned previously is that I'm using the Hot Reload to edit some layouts on the fly and doing some changes in the code while running a debug session and is in-between debug sessions that the error has been occurring. I'll try to be aware of my actions to see if I can provide a more meaningful report later.
3. There was an error that would popup when I tried to navigate to a definition of a class or element. When everything is okay I'm able to navigate to the correct definition, but when the bug is occurs I'm unable to do it, be it from a .xaml file or a .cs file. I'll keep an eye on any popup warnings that might appear and will try to capture screenshots when they happen.

I apologize for not being able to provide more information for now, will keep an eye next Monday to see if I can make it happen again.

from vscode-csharp.

Hi @dibarbet

Since I've reported this issue I tried to update the .NET MAUI Extension to version v1.1.14 (pre-release) and in this version the issue hasn't happened so far. Unfortunately since this speeds up a bit things on my side I can't revert to the previous version for some time.

Meanwhile I've managed to catch the error that happened at the same time before:

Unsure if it's 100% the same error, but I do remember being very similar to this one (when trying to go to definition of an element in .xaml, for example a custom element, it would popup the error message and wouldn't navigate).

from vscode-csharp.

Right before I hit send, I went back to vscode to confirm. And voilà, suddenly intellisense had kicked in. Not sure what the take from this should be, but maybe there is missing an indicator that things are still loading?

@danosted by any chance was the Projects spinner in the bottom left spinning? Or was it displaying a static list of projects

from vscode-csharp.

Hi @dibarbet

Since I've reported this issue I tried to update the .NET MAUI Extension to version v1.1.14 (pre-release) and in this version the issue hasn't happened so far. Unfortunately since this speeds up a bit things on my side I can't revert to the previous version for some time.

Meanwhile I've managed to catch the error that happened at the same time before:

Unsure if it's 100% the same error, but I do remember being very similar to this one (when trying to go to definition of an element in .xaml, for example a custom element, it would popup the error message and wouldn't navigate).

Interesting - that error message is helpful. Looks like its trying to navigate to a source generated file which isn't supported yet, see #6426

However I don't think that should cause colorization and everything else to disappear. I'm glad 1.1.14 is working better so far, but let me know if the issue occurs again. I'd also be interested if you see it again. There are some project load issues we're working on as well which might be contributing. Hope to have those fixed next week.

from vscode-csharp.

Closing this issue since it sounds like the original issue is isn't occuring. Additionally, we uploaded a new prerelease version last week (2.39.28) which fixed some (potentially related) issues with intellisense disappearing.

from vscode-csharp.