cake-build / cake-build/cake-vscode
Fix IntelliSense not working sometimes when it cannot find the Cake .NET Global Tool
- Dominant language
- TypeScript
- Stars
- 45
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
... Once https://github.com/cake-build/bakery/issues/125 is fixed.
---
It seems that in some scenarios the .NET Global Tool is installed and appears to be in the `%PATH%` but when you actually try to run it (e.g. via `Process.Start`) the OS can't find it for some reason.
[I mentioned this issue before on Slack](https://cake-build.slack.com/archives/C03B4CZ10/p1612124902111000?thread_ts=1612123753.104600&cid=C03B4CZ10) and recently @AndaBucsa [reported a similar issue](https://github.com/cake-build/cake/discussions/3171).
I also had a very similar issue with the Rider extension and @nils-a was able to fix it in https://github.com/cake-build/cake-rider/issues/78 by searching for the .NET Tool in the expected installation path `%USERPROFILE%\.dotnet\tools\` (Windows) and `$HOME/.dotnet/tools/` (Unix-like), and we think [the same fix could be applied to Bakery](https://github.com/cake-build/bakery/issues/125).
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by checking the dependency in bakery/issues/125 and compare the related fix described in cake-rider/issues/78. Investigate how the VS Code extension launches the Cake .NET Global Tool when it is present in %PATH%. Done means IntelliSense works when the tool is installed in %USERPROFILE%\.dotnet\tools\ or $HOME/.dotnet/tools/.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100