Chet Husk

No, there's no good way. In addition, our current mechanism is incomplete because the file could belong to multiple projects.

In case you haven't seen it, [slngen](https://microsoft.github.io/slngen/) is some prior art in this space.

Thanks for the report! I'd start investigating this by adding a test [to the existing method-based tests](https://github.com/fsharp/FsAutoComplete/blob/main/test/FsAutoComplete.Tests.Lsp/InlayHintTests.fs#L1143-L1194), and then debug into [the implementation of the feature](https://github.com/fsharp/FsAutoComplete/blob/main/src/FsAutoComplete.Core/InlayHints.fs#L972-L1010) to see where the...

If you open the VSCode developer tools (there's a command for this in the command palette) and scroll to the top, some of the first details should be about how...

@DmitryVil can you click the 'more details' button in the error pop up and provide the content it shows?

In the screenshot you uploaded to this issue it's the blue button on the bottom-right of the pop-up. Do you still see that on your local VSCode notifications?

If you fix the slashes, does that path exist and have data?

And you do in fact have `dotnet` installed an on your PATH? You can open a terminal and successfully run `dotnet --info`?

do you have `FSharp.dotnetRoot` set anywhere in your config? if so you should remove it, because you have an otherwise-correct dotnet install.

You seeing this error means you've hit [this code path](https://github.com/ionide/ionide-vscode-fsharp/blob/af58c42ea446e28e4cba5d373d193888cea4e6f5/src/Core/LanguageService.fs#L195-L211). This `Environment.tryGetTool` call calls `cmd /C where dotnet` to try and discover `dotnet` binaries on your PATH. Here's an example...