Allow User to "Bring Their Own" Runtime for the Language Server for VS Code Extension
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1k
- Forks
- 131
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Is your feature request related to a problem? Please describe.
As reported in #565 some users prefer not to have the .NET Install Tool for Authors obtain the .NET Runtime and may want to provide their own.
Describe the solution you'd like
A mechanism by which the user can specify a path to dotnet.exe that the VS Code extension will respect, and if present, not call dotnet.acquire.
Describe alternatives you've considered
We could alternately just try to run dotnet path\to\LanguageServer.dll and if that fails, acquire the Runtime as needed, but the server is implicitly started by the client so this may not be the best approach.
Additional context
This is a feature available in the VS Code extension for Bicep. https://github.com/Azure/bicep/blob/6fd52773948a97f11a776b9fbbf16fc03439af90/src/vscode-bicep/src/language/client.ts#L164-L172
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the VS Code extension's language-server startup path and where it calls dotnet.acquire. Compare the referenced Bicep client behavior, then define how a user-specified dotnet.exe path is supplied and respected. Done means the extension uses that runtime when configured and skips runtime acquisition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100