Editor Setup
SharpLsp is editor-agnostic at the protocol layer. VS Code is the supported, packaged client today; the other integrations remain development work.
VS Code
Install SharpLsp from the VS Code Marketplace. The VSIX includes the Rust host and the C# and F# sidecars, so no separate SharpLsp installation is needed.
During activation the extension:
- locates a compatible .NET 10 SDK or acquires one through Microsoft's .NET Install Tool;
- resolves the bundled binaries for the current platform;
- starts the language client and sidecars;
- discovers a solution or project in the workspace.
The extension also supplies the Solution Explorer, NuGet browser, profiler, debugger integration, test CodeLens, F# Interactive commands, build commands, and status/output views.
Workspace Trust
In an untrusted workspace, SharpLsp runs only its bundled binaries. Workspace values that could select an executable or inject arguments—such as sharplsp.lspPath, sidecar paths, extra server arguments, FSI arguments, and the debug-adapter path—are ignored until the workspace is trusted.
Custom Development Binaries
In a trusted workspace, the sharplsp.lspPath, sharplsp.csharpSidecarPath, and sharplsp.fsharpSidecarPath settings can point the extension at local development builds. Leave them empty for the bundled release binaries.
Other LSP Clients
A generic editor can speak LSP 3.17 to the host over stdio, but SharpLsp does not yet publish a supported standalone installation workflow that stages the host and both sidecars for those clients. Zed, Neovim, Rider, Helix, and Emacs integrations are planned, not current release surfaces.
For repository builds, see Contributing.