Support language features in metadata / decompiled source files

[dibarbet]

Currently it looks like all metadata as source files are going into the LSP misc workspace. This appears to be because TryAddDocumentToWorkspace never gets called. In VS this is called when the file is opened (the misc files workspace sees it and puts the document in the workspace). Since a solution is never created in the metadata workspace because the file is never added, the metadata workspace is also not registered.

[dibarbet]

Scenarios here

1. Go to definition from metadata references
2. Document outline - https://github.com/dotnet/vscode-csharp/issues/6341

[daniel-tonic]

Is there any update on this? This seems like a pretty big miss from a feature-parity perspective and it's been several months since this ticket was updated.

[hsm207]

Just encountered #6021 but only for some projects in a solution.

I'm on version 2.22.5 and everytime I reload the window, the C# output pane shows this:

Using dotnet configured on PATH
Dotnet path: /usr/share/dotnet/dotnet
Activating C# + C# Dev Kit...
waiting for named pipe information from server...
[stdout] {"pipeName":"/tmp/c8da874b.sock"}
received named pipe information from server
attempting to connect client to server...
client has connected to server
[Info  - 3:42:10 AM] [Program] Language server initialized
[Error - 3:42:11 AM] Request textDocument/semanticTokens/range failed.
  Message: Unsupported extension '' and LSP language id ''
  Code: -32000 
[object Object]
[Error - 3:42:11 AM] Request textDocument/semanticTokens/range failed.
  Message: Unsupported extension '' and LSP language id ''
  Code: -32000 
[object Object]