Ignas

> **Edit**: I've just noticed that `textDocument/definitions` from _within_ a source generated buffer errors, unlike from within a `$metadata$` buffer: As far as I could see this is not supposed...

Only took almost a year, but the latest version should support source generated files on all commands

Hi, So my guess is that after the restart LSP client is no longer attached to the buffer (`:LspInfo` shows this). The plugin [manually attaches the client](https://github.com/Hoffs/omnisharp-extended-lsp.nvim/blob/main/lua/omnisharp_extended.lua#L61) when creating these...

> I think it might be related to current directory. I can force this to happen every time by running go-to-def on a dll, then running `:cd `, then trying...

With latest update this no longer seems to be an issue, when modifying current directory, please reopen if you're still experiencing this

Hi, could you include output of LSP log (can be opened with `:LspLog`) and maybe a snippet of solution where you are getting this? And your config possibly.

closing the issue, if you're still having issues with latest version, please reopen this issue or create a new one

With tools such as https://github.com/grafana/phlare or https://github.com/parca-dev/parca leveraging pprof and continuous profiling becoming a thing ( https://www.cncf.io/blog/2022/05/31/what-is-continuous-profiling/ ) it would be cool to see this.

As I understand #49 should have resolved this

Hi, I don't really understand the second part of the question. As for the first part, I am not entirely sure if omnisharp supports multiple solutions, is there something that...