dsh-lsp-csharp

dsh-lsp-csharp

C# language configuration pack for DeepSeek Harness (DSH). OmniSharp (default) — the C# language server; Roslyn-based server as an alternative. 中文：DSH 的 C# LSP「即插即用」语言包 —— 装上本包，.cs 文件即可用 lsp 工具做代码导航。

This pack is one Cordis configuration plugin: it registers a configured @deepseek-ai/dsh-lsp-stdio instance on ctx.lsp with the server command, launch arguments, and extension mapping for C#. It implements no LSP protocol — the shared base does: @deepseek-ai/dsh-lsp (the seam) + @deepseek-ai/dsh-tool-lsp (the model-facing lsp tool with goToDefinition / findReferences / goToImplementation / hover). Twelve packs reuse one unchanged base.

Installing the language server

OmniSharp ships as an OmniSharp.dll (the omnisharp-roslyn build); some package managers expose an omnisharp executable. Either way it is launched with stdio, for example:

dotnet /absolute/path/to/OmniSharp.dll --stdio

Override the pack config to match your install:

- id: lsp-csharp
  name: '@dsh-lsp-packs/dsh-lsp-csharp'
  config:
    command: dotnet
    args:
      - /absolute/path/to/OmniSharp.dll
      - --stdio

Requires the .NET SDK (or Mono). The modern Roslyn-based server (Microsoft.CodeAnalysis.LanguageServer) is a drop-in alternative with the same command/args shape. See the upstream anthropics/claude-plugins-official csharp-lsp README for the same guidance.

⚠️ The plugin itself never downloads or installs the server binary — matching the upstream anthropics LSP plugins, the server is an external prerequisite. The plugin only resolves and launches it.

Supported extensions

| .cs | csharp |

How the pack works

• Lazy start: the server process is not started at load. lsp-stdio launches it lazily on the first matching query and keeps one process per workspace.
• No-server fallback: if the executable cannot be resolved, the pack still loads; every lsp query for these extensions fails with a structured LSP_UNAVAILABLE error naming the command — the rest of the session is unaffected.
• Config overrides: every default below can be overridden from the composition row, e.g. a server installed at a non-standard path:

- id: lsp-csharp
  name: '@dsh-lsp-packs/dsh-lsp-csharp'
  config:
    command: /absolute/path/to/omnisharp
    args:
      - --stdio
    extensionToLanguage:
      '.xyz': custom-language-id
    maxDocumentBytes: 8000000

All fields of the servers table documented in the @deepseek-ai/dsh-lsp-stdio README are accepted (command, args, env, extensionToLanguage, initializationOptions, configuration, byte/time bounds).

Mounting

1. Mount the shared base once (the lsp service, the lsp tool, and a filesystem/subprocess pair for the same execution world) — ready-made snippet in examples/base-composition.cordis.yml of the dsh-lsp-packs repo.
2. Install the pack (its cordis.yml is the dsh.bundle.patch, so the row inserts itself):

dsh plugin add @dsh-lsp-packs/dsh-lsp-csharp    # published name
dsh plugin add /path/to/dsh-lsp-packs/dsh-lsp-csharp  # or a local checkout

or compose the row directly (name resolved from the installed package):

- insert:
    - id: lsp-csharp
      name: '@dsh-lsp-packs/dsh-lsp-csharp'

Smoke test

pnpm vitest run --dir dsh-lsp-csharp   # or from the repo root: pnpm test

• Lane 1 (offline): asserts the defaults (command / args / extension table / provider id).
• Lane 2 (offline): asserts the missing-server fallback returns LSP_UNAVAILABLE.
• Lane 3 (needs the server): runs the four lsp operations against Sample.cs; it auto-skips when omnisharp is not on PATH.

OmniSharp works best inside a .sln/.csproj; the smoke test writes a bare file and the same-file definition still resolves in most configurations.

License

MIT — see LICENSE. The server binary is a third-party component with its own license.